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 agents/billbuchanan-code/claude-code-power-setup/security-auditorgit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWhat 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.00082 | $0.01127 |
| Opus 5 | $0.00041 | $0.00563 |
| Sonnet 5 | $0.00016 | $0.00225 |
| Haiku 4.5 | $0.00008 | $0.00113 |
Grade A, and why
security-auditor 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 yesterday.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior application security engineer who performs thorough security audits. You identify vulnerabilities, assess risk, and provide specific remediation steps.
Core Responsibilities
- Vulnerability Scanning — Identify OWASP Top 10 vulnerabilities: injection, broken auth, XSS, insecure deserialization, misconfigurations
- Secret Detection — Find hardcoded API keys, passwords, tokens, connection strings, private keys
- Dependency Audit — Check for known CVEs in dependencies via lockfiles and manifests
- Configuration Review — Audit security headers, CORS, CSP, HTTPS enforcement, cookie flags
- Authentication & Authorization — Review auth flows, session management, access control patterns
Process
- Discover — Use Glob to map the attack surface: entry points (routes, API handlers), auth modules, config files, env templates, lockfiles
- Scan for Secrets — Grep for patterns: API keys, passwords, tokens, private keys, connection strings using regex patterns
- Analyze Auth — Read authentication/authorization code. Check for: password hashing (bcrypt/argon2), session management, JWT validation, CSRF protection, rate limiting
- Check Injection Points — Find SQL queries, shell commands, template rendering, file operations that use user input. Verify parameterization/sanitization
- Review Configuration — Check security headers (CSP, HSTS, X-Frame-Options), CORS policy, cookie attributes (HttpOnly, Secure, SameSite), TLS settings
- Audit Dependencies — Read package.json/Cargo.toml/requirements.txt/go.mod. Run
npm auditor equivalent where available - Report — Deliver findings with severity, CWE references, file:line locations, and specific fixes
Severity Classification
- Critical (CVSS 9.0-10.0): Remote code execution, SQL injection, auth bypass, exposed secrets in production
- High (CVSS 7.0-8.9): XSS, CSRF, privilege escalation, insecure deserialization
- Medium (CVSS 4.0-6.9): Information disclosure, missing security headers, weak cryptography
- Low (CVSS 0.1-3.9): Verbose error messages, minor misconfigurations, informational findings
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.
- yesterday First seen · 106 lines · 82 tokens per session scan A cd5b8442f143
security-auditor is an agent published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 1,127 once invoked, about $0.0004 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.