Skip to content

legioncodeinc/code-audit-tools

v3.0.0AGPL-3.0-or-later

Audit repositories and app security, measure bloat, inspect branches and plan remediation.

Code Audit Tools

Audit repositories and app security, measure bloat, inspect branches and plan remediation.

Code and owned-app investigation use source/effect evidence and stack-specific security. They must not inherit passive website permissions.

Requires wasp-nest-core.

Choose a capability

This pack contains 12 skills, 11 agents and 1 source command. The table explains each source skill; open its linked instructions for exact inputs, outputs and limits.

SkillWhat it does and when to use it
audit-my-code-stingerOrchestrates /audit-my-code. Five tiers (foundation, vibe, basic, full, mario) of codebase audits, dispatched to paired Drones and delivered as a Legion Code Inc. brief.
code-audit-brief-stingerRender the Audit My Code brief, one self-contained Field Guide styled HTML file per run, from the workspace only. Escapes repo text, merges duplicates, prints cleanly to PDF.
code-bloat-stingerRead-only bloat audit of any repo. jscpd duplication, knip or language dead-code tools with a spot-check, cloc size, function and closure structure, split plans, banded verdict.
code-forensics-stingerReview software vendor engagements using contracts, invoices, messages and delivery records. Produce cited evidence drafts for human or counsel review.
code-foundation-stingerRead-only repo health audit: Wasp Nest setup, agent readiness, CI, tests, lint, lockfiles, secrets, governance. Writes contract-shaped foundation findings and measures.
lovable-audit-stingerAudit Lovable-built Supabase apps: RLS denials, role-differential reads, function gating, auth posture, bundle-forensics key/endpoint extraction, findings triage, reporting.
nextjs-security-stingerDeep Next.js security audit (13 to 16, App and Pages Router). Version advisories, proxy and middleware auth, Server Actions, Route Handlers, data exposure, caching, config.
polyglot-security-stingerDeep security audit for Node servers, Python, Go, Rust, Rails, PHP, Spring, and .NET, plus secrets, dependencies, SAST, and CI. Read-only, writes Audit My Code findings.
react-security-stingerReview React 18/19 security, including Next.js clients. Covers XSS, secrets and client trust.
remediation-planning-stingerPlan fixes from audit findings. Clusters findings into work packages, orders Now, Next, Later, and with approval writes Library PRDs, IRDs, knowledge docs, and draft contracts.
sveltekit-security-stingerEvidence-backed, read-only security audit of Svelte 4/5 and SvelteKit 2 apps, any stack. Versions vs advisories, load leaks, actions, remote functions, hooks, XSS, CSRF, adapters.
swarm-audit-stingerSwarm audit of a repository: Workflow fleet of single-lens Sonnet investigators, adversarial verification, Opus interpreters and critic, 10-minute check-ins, kill and respawn, nothing unreviewed.

Start one task

Required packs: wasp-nest-core

Install the selected pack and its prerequisites through the marketplace. For the version 3 layout, purge the previous installation first. Select the skill shown by your client, or paste this request with real paths and scope:

After adding the Wasp Nest marketplace, Claude Code uses these installation instructions:

/plugin install wasp-nest-core@wasp-nest
/plugin install code-audit-tools@wasp-nest

Other clients use their plugin selection UI or discovered skill selector. Installing a package and invoking a task are separate steps.

Use audit-my-code-stinger to audit [repository]. State the audit tier and scope before reading it, and deliver findings without changing the audited code.

Expected result: Evidence-backed code findings and the audit brief. Remediation planning is a separate step.

Claude Code plugin command names:

CommandWhat it does
/code-audit-tools:audit-my-code (procedure)Audit a codebase the way Legion Code Inc. does: foundation health, duplication and dead code, framework-deep security, quality, and a remediation plan, delivered as a branded brief.

Agent responsibilities

AgentResponsibilityPaired skill
code-audit-brief-wasp-droneRenders the Audit My Code brief, one self-contained Field Guide styled HTML file per run, from the run workspace.code-audit-brief-stinger
code-bloat-wasp-droneRead-only code bloat audit for the bloat dimension of /audit-my-code.code-bloat-stinger
code-forensics-wasp-droneReview software and agency engagements from supplied contracts, invoices, communications and delivery evidence.code-forensics-stinger
code-foundation-wasp-droneFoundation (health) audit of a code repository for /audit-my-code.code-foundation-stinger
lovable-audit-wasp-droneEmpirical security audit of Lovable-built Supabase apps: row-level-security denial verification, role-differential visibility probes, Edge Function gating checks, auth-posture readout, client-bundle key and endpoint forensics, findings triage against an operator risk taxonomy, and grounded reporting.lovable-audit-stinger
nextjs-security-wasp-droneDeep, evidence-backed Next.js security audit (versions 13 to 16, App and Pages Router) for an /audit-my-code run.nextjs-security-stinger
polyglot-security-wasp-droneDeep, read-only security audit of non-React, non-Next.js, non-SvelteKit code (Node servers, Python, Go, Rust, Rails, PHP, Spring, .NET) plus secrets, dependencies, static analysis, and CI/CD and infrastructure, writing SEC-POLY findings in the Audit My Code contract shape.polyglot-security-stinger
react-security-wasp-droneDeep, evidence-backed security audit of React 18 and 19 code for /audit-my-code.react-security-stinger
remediation-planning-wasp-droneTurns Mario Audit findings into a remediation roadmap (Now, Next, Later), plan.json, and, only with approval of the exact file list, Library PRDs, IRDs, knowledge docs, and draft contracts.remediation-planning-stinger
sveltekit-security-wasp-droneDeep, evidence-backed, read-only security audit of Svelte 4/5 and SvelteKit 2 apps (and plain Svelte + Vite SPAs) on any stack, for an /audit-my-code run.sveltekit-security-stinger
swarm-audit-wasp-droneSwarm-audit scout, observer, and assembler.swarm-audit-stinger

Codex can use the named skill or its generated source-command-<name> wrapper where a source command exists. Home installations may expose flat commands. Use the actual selector offered by the host. A pack with no paired agents runs its standalone skills directly; a skill name does not prove that a native agent was launched.

Prerequisites and boundaries

No extra workflow-specific pack prerequisite is declared. Tool and account requirements remain in each skill.

Core supplies shared routing and review methods. Native Codex role registration requires the explicit installed-plugin registry and trusted Core hook; a marketplace selection alone is not proof of registration. Read the linked skill before work. Missing source, browser, connector, renderer or account access is a reported gap. Installation does not authorize sending, publishing, paid work or live settings changes.