code-audit-tools — Claude Code plugin for repo and security audits
code-audit-tools — a plugin for Claude Code and Codex that runs read-only audits across repositories: duplication, dead code, framework security, and CI health. Delivers findings as a printable HTML brief.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install code-audit-tools@wasp-nestWhat code-audit-tools does
The plugin targets Claude Code and Codex. It ships 12 skills, 11 sub-agents, and one slash command. The top-level entry point is /code-audit-tools:audit-my-code, which dispatches across five audit tiers: foundation, vibe, basic, full, and mario. Under the hood each tier routes work to paired drones — specialised read-only sub-agents that never touch the audited code.
Security coverage splits by stack. nextjs-security-stinger handles Next.js versions 13 through 16, App and Pages Router. react-security-stinger covers React 18 and 19. sveltekit-security-stinger targets Svelte 4/5 and SvelteKit 2. polyglot-security-stinger picks up everything else: Node servers, Python, Go, Rust, Rails, PHP, Spring, and .NET. Lovable-built Supabase apps get their own skill, lovable-audit-stinger, which probes RLS denials, role-differential reads, and client-bundle key exposure.
Results are assembled into a self-contained Field Guide HTML file per run, escaped and deduplicated, ready to print to PDF. Remediation planning is a separate step: remediation-planning-stinger clusters findings into Now, Next, and Later work packages. The plugin requires wasp-nest-core — installation fails without it.
What it helps with
- Detect code duplication and dead exports across a repository
- Run a deep security audit on a Next.js 13–16 application
- Check RLS policies and auth posture in a Lovable-built Supabase app
- Cluster audit findings into prioritised remediation packages
- Generate a self-contained HTML audit brief exportable to PDF
Example prompts for the agent
- Run
/code-audit-tools:audit-my-codeon this repo at the full audit tier - Use
audit-my-code-stingerto audit./src— state the tier and scope before reading any files - Run
lovable-audit-stingeron this Supabase project and report RLS and auth findings
How to install code-audit-tools
Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install code-audit-tools@wasp-nestStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about code-audit-tools
How do I install code-audit-tools in Claude Code?
Run two commands in order: first /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install code-audit-tools@wasp-nest. Install wasp-nest-core separately before these steps.
What does the code-audit-tools plugin do?
It audits repositories in read-only mode, covering duplication, dead code, framework-specific security, and CI health. Output is an HTML report with findings; remediation planning runs as a separate skill.
Which frameworks does the security audit cover?
Next.js (13–16), React 18/19, SvelteKit 2 / Svelte 4–5, and server-side stacks including Node, Python, Go, Rust, Rails, PHP, Spring, and .NET.