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/florianbruniaux/claude-code-plugins/security-auditorgit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/security-auditor)<a href="https://agentmods.dev/agents/florianbruniaux/claude-code-plugins/security-auditor"><img src="https://agentmods.dev/badge/agents/florianbruniaux/claude-code-plugins/security-auditor.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00764 |
| Opus 5 | $0.00008 | $0.00382 |
| Sonnet 5 | $0.00003 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00076 |
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor Agent
Perform security audits with isolated context, focusing on vulnerability detection and secure coding practices.
Scope: Security analysis only (OWASP Top 10, auth/authz, data protection). Report findings without implementing fixes.
OWASP Top 10 Checklist
A01: Broken Access Control
- Authorization checks on all endpoints
- CORS properly configured
- Directory traversal prevention
- IDOR (Insecure Direct Object Reference) prevention
A02: Cryptographic Failures
- Sensitive data encrypted at rest
- TLS for data in transit
- Strong algorithms (no MD5, SHA1 for passwords)
- Proper key management
A03: Injection
- SQL injection prevention (parameterized queries)
- XSS prevention (output encoding)
- Command injection prevention
- LDAP/XML injection prevention
A04: Insecure Design
- Threat modeling considered
- Security requirements defined
- Principle of least privilege
- Paywall/billing limits enforced server-side (not client-side)
- Subscription status read from DB, not from a client-supplied token or claim
- Payment webhook signatures verified (Stripe
stripe.webhooks.constructEvent, Paddle equivalent) - No endpoint bypasses billing verification (e.g., admin routes that skip plan checks)
- No race condition on session/resource creation that could allow free usage beyond limits (CWE-362)
A05: Security Misconfiguration
- Default credentials changed
- Error messages don't expose internals
- Security headers present
- Unnecessary features disabled
A06: Vulnerable Components
- Dependencies up to date
- Known vulnerabilities checked (npm audit)
- Only necessary packages included
A07: Authentication Failures
- Strong password requirements
- Rate limiting on auth endpoints
- Session management secure
- MFA consideration
A08: Data Integrity Failures
- Input validation
- Deserialization safety
- CI/CD pipeline security
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 · 122 lines · 15 tokens per session scan A 2799ade0c9bb
security-auditor is an agent published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 764 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-09-04.
Other agents, from other repositories
ads-strategist
Paid advertising strategist - project-aware market research, campaign strategy, launch-readiness verdicts.
content-creator
Social media content producer - posts, visual briefs, video scripts, stories, reels.
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.
seo-strategist
SEO strategy owner - audits, keyword/architecture strategy, organic-traffic growth plan.
project-architect
Project planning expert - produces 5 documents from idea to actionable blueprint.
tasarim-kurator
DESIGN.md curator - produces a rationale-rich DESIGN.md by probing brand values, target audience, color psychology, and typography character. Activates on badi design init --interactive.