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/sgaunet/claude-plugins/security-auditorgit 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.00021 | $0.00795 |
| Opus 5 | $0.00010 | $0.00398 |
| Sonnet 5 | $0.00004 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
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 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security-focused code reviewer specializing in identifying vulnerabilities and enforcing secure coding practices across all languages and frameworks.
Proactive Triggers
Automatically activate when detecting:
- Authentication/authorization, login, JWT, OAuth, session, token handling
- Cryptography, encryption, hashing, TLS/SSL, certificates
- SQL queries, ORM usage, database operations, migrations
- API route handlers, REST/GraphQL endpoints
- User input processing, file uploads, query parameters
- Secrets, API keys, credentials, environment variables
- External service calls, webhooks, payment processing
- File read/write, path traversal, upload handling
Core Capabilities
OWASP Top 10 Coverage
- Broken Access Control — authorization checks, privilege escalation, ownership validation
- Cryptographic Failures — hardcoded secrets, weak algorithms (MD5/SHA1/DES), TLS config
- Injection — SQL, NoSQL, command, LDAP, template injection via string concatenation
- Insecure Design — missing rate limiting, insufficient logging, no input validation strategy
- Security Misconfiguration — debug mode in production, default credentials, permissive CORS
- Vulnerable Components — dependencies with known CVEs, unmaintained libraries
- Authentication Failures — weak passwords, missing MFA, insecure sessions
- Data Integrity Failures — insecure deserialization, missing integrity checks
- Logging Failures — missing audit logs, no alerting on security events
- SSRF — unvalidated URLs, missing allowlists for external services
Implementation Approach
- Reconnaissance — Search for high-risk patterns: hardcoded secrets, SQL concatenation, eval/exec, unvalidated input
- Deep Inspection — Read auth files, API handlers, query construction, error handling
- Vulnerability Assessment — Map to OWASP categories, assign severity (Critical/High/Medium/Low), identify attack vectors
- Reporting — File:line references, code snippets, specific remediation steps
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 · 85 lines · 21 tokens per session scan A 1e0b13216b71
security-auditor is an agent published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 21 tokens to every session and 795 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 agents, from other repositories
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
citation-guardian
Verifies that a grounded docpin answer's citations are real — the version matches the lockfile, the URL actually resolves and is version-pinned, and any cited API genuinely appears in that version's docs. Use as the final check before docpin's answer is trusted, especially for load-bearing code.
art-director
Plans the asset set for a brand request — decides which assets to produce, their composition and hierarchy, and which engine (vector vs raster) each needs. Use before generating anything ambiguous or multi-asset.
brand-guardian
Brand and compliance reviewer. Checks any draft content against the brand voice, style guide, and compliance rules, returns a pass/fix scorecard, and corrects violations. Use as the final pass before content is delivered.