Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/sgaunet/claude-plugins/audit-codebasegit clone --depth 1 https://github.com/sgaunet/claude-pluginsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00014 | $0.01199 |
| Opus 5 | $0.00007 | $0.00600 |
| Sonnet 5 | $0.00003 | $0.00240 |
| Haiku 4.5 | $0.00001 | $0.00120 |
Grade A, and why
audit-codebase scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Codebase Command
Audit the code for potential security vulnerabilities, performance issues, and adherence to best practices. Provide a detailed report with recommendations for improvements.
Process
-
Discover Codebase Structure: Use
GlobandBashto identify key directories and file types to audit. -
Launch 3 parallel Sonnet agents to independently audit different aspects of the codebase:
Agent #1: Security Auditor
- Check for exposed secrets or sensitive data
- Validate input handling to prevent injection attacks
- Ensure proper authentication and authorization mechanisms
- Review error handling to avoid information leakage
- Verify use of secure libraries and dependencies
- Return findings in format:
{severity: "CRITICAL"|"HIGH"|"MEDIUM"|"LOW", file: "path/to/file.ext", line: N, finding: "...", recommendation: "..."}
Agent #2: Performance Analyzer
- Identify and optimize slow or inefficient code paths
- Analyze memory usage and detect potential leaks
- Review database queries for performance issues
- Evaluate caching strategies and their effectiveness
- Return findings in format:
{severity: "CRITICAL"|"HIGH"|"MEDIUM"|"LOW", file: "path/to/file.ext", line: N, finding: "...", recommendation: "..."}
Agent #3: Best Practices Reviewer
- Ensure adherence to coding standards and style guides
- Review documentation for completeness and clarity
- Evaluate test coverage and effectiveness
- Identify opportunities for code simplification and refactoring
- Return findings in format:
{severity: "CRITICAL"|"HIGH"|"MEDIUM"|"LOW", file: "path/to/file.ext", line: N, finding: "...", recommendation: "..."}
-
Aggregate Results: Collect findings from all 3 agents and merge into unified report.
-
Prioritize Findings: Sort by severity (Critical → High → Medium → Low) within each category.
Agent Invocation Examples
Use the Task tool to launch agents in parallel:
Task(subagent_type: "security-auditor", model: "sonnet", prompt: "Audit codebase for security vulnerabilities. Focus on: exposed secrets, injection attacks, auth mechanisms, error handling, dependency security. Return findings with severity levels.")
Task(subagent_type: "general-purpose", model: "sonnet", prompt: "Analyze codebase for performance issues. Focus on: inefficient code paths, memory leaks, database queries, caching strategies. Return findings with severity levels.")
Task(subagent_type: "general-purpose", model: "sonnet", prompt: "Review codebase for best practices adherence. Focus on: coding standards, documentation, test coverage, refactoring opportunities. Return findings with severity levels.")
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 107 lines · 14 tokens per session scan A 0afa4d0c5ff5
audit-codebase is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 14 tokens to every session and 1,199 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
analyze-test
Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.