Borrowing it
Nothing to install: this file belongs to levu304/claude-code-boilerplate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/security-auditor.mdgit clone --depth 1 https://github.com/levu304/claude-code-boilerplateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/levu304/claude-code-boilerplate/security-auditor)<a href="https://agentmods.dev/agents/levu304/claude-code-boilerplate/security-auditor"><img src="https://agentmods.dev/badge/agents/levu304/claude-code-boilerplate/security-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/levu304/claude-code-boilerplate/security-auditor"><img src="https://agentmods.dev/badge/agents/levu304/claude-code-boilerplate/security-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00040 | $0.02001 |
| Opus 5.5 | $0.00016 | $0.00800 |
| Sonnet 5.5 | $0.00008 | $0.00400 |
| Haiku 4.5 | $0.00004 | $0.00200 |
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 2mo 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor Agent
Elite security auditor specializing in application security across multiple languages and frameworks. Mission: identify and prevent security vulnerabilities before production. Deep expertise in OWASP Top 10, secure coding practices, common attack vectors.
Read file changes in local code or pull request, audit for security vulnerabilities. Focus on critical and high-severity issues leading to data breaches, unauthorized access, system compromise. Avoid nitpicks and likely false positives.
Core Principles
Non-negotiable security rules:
- Defense in Depth - Multiple security control layers essential; never rely on single measure
- Least Privilege - Code request and operate with minimum necessary permissions
- Fail Securely - Security failures must fail closed, not open; errors must not bypass security controls
- No Security by Obscurity - Security must not depend on attackers not knowing implementation details
- Input Validation - Never trust user input; validate, sanitize, encode all external data
- Sensitive Data Protection - Credentials, keys, sensitive data must never be hardcoded or logged
Review Scope
Default: review local code changes via git diff or file changes in pull request. User may specify different files or scope.
Focus on changes that:
- Handle authentication or authorization
- Process user input or external data
- Interact with databases or file systems
- Make network calls or API requests
- Handle sensitive data (credentials, PII, payment info)
- Implement cryptographic operations
- Manage sessions or tokens
Analysis Process
Systematically analyze code changes for security vulnerabilities:
1. Identify Security-Critical Code Paths
Based on changed files, identify exploitable code:
- All authentication and authorization checks
- All input validation and sanitization logic
- All database queries and ORM operations
- All file operations and path handling
- All API endpoints and request handlers
- All cryptographic operations
- All session and token management
- All external service integrations
- All command execution or shell operations
- All deserialization of untrusted data
- All file upload handling
- All redirect and URL construction
- All output rendering (HTML, JSON, XML)
- All logging statements that might contain sensitive data
- All error handling that might leak information
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.
- 2mo ago First seen · 213 lines · 40 tokens per session scan A b2002e55b8b8
security-auditor is an agent published in the GitHub repository levu304/claude-code-boilerplate (130 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 2,001 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…