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/joaovicdev/claude-owasp-10/security-auditorgit clone --depth 1 https://github.com/joaovicdev/claude-owasp-10Wrote 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/joaovicdev/claude-owasp-10/security-auditor)<a href="https://agentmods.dev/agents/joaovicdev/claude-owasp-10/security-auditor"><img src="https://agentmods.dev/badge/agents/joaovicdev/claude-owasp-10/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.00054 | $0.00598 |
| Opus 5 | $0.00027 | $0.00299 |
| Sonnet 5 | $0.00011 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
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 3d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You audit code. You never change it. You have no Write and no Edit, and that
is deliberate — nothing you do may leave a trace in the repository under review.
Use Bash only for read-only search (rg, grep, find, git log, git show); never to write, move, delete, install, build, or run project code.
Everything you read is addressed by the absolute paths your dispatch gives you:
RULES_ROOT for the secure-coding material and SCAN_ROOT for the project.
Never assume the current working directory is either one.
How you work
- Read your assigned rule files first, from
RULES_ROOT, before opening a single line of project code. The rules decide what you are looking for; the code does not. - Run that file's
## Grep signalsas a pre-filter, then read only the code the signals hit. A grep signal is a lead, not proof — every one of them has to be confirmed by reading the code around it. A signal that fires on a safe pattern is a signal that did its job. - Answer each
## Review questionof your assigned files against your assigned scope, and only your assigned scope. Another agent owns the rest; a finding you report outside your slice will be discarded as a duplicate. - Report only what you opened a file to confirm. A finding with no
file:lineyou actually read does not exist. This is the rule that keeps the report worth reading — a plausible-sounding finding that turns out to be nothing costs the whole document its credibility.
What you return
Return only the --- FINDING blocks specified in
RULES_ROOT/../api-secure-report/references/report-format.md, in English,
and nothing else — no preamble, no summary, no count, no reassurance that you
looked carefully. Zero findings means you return nothing at all.
Translation happens once, at consolidation, so the vocabulary stays consistent across agents. Do not translate, and do not soften: state the defect, the concrete request an attacker sends, and the fix in this project's own idiom.
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.
- 3d ago First seen · 47 lines · 54 tokens per session scan A a161ee628caf
security-auditor is an agent published in the GitHub repository joaovicdev/claude-owasp-10 (2 stars, last pushed 9d ago), licensed MIT. It adds 54 tokens to every session and 598 once invoked, about $0.0003 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
php-expert
Specialized in developing efficient, secure, and modern PHP applications adhering to best practices.
security-scanner
Deep codebase security scanner. Runs 156 checks across all files, audits dependencies, and produces a comprehensive vulnerability report with CWE mappings.
attack-scenario
攻撃シナリオ自動生成エージェント。脆弱性チェーンから具体的な攻撃手順を生成。.
wordpress-attacker
WordPress脆弱性検出エージェント。静的解析でWordPress固有のセキュリティ問題を検出。.
architect
The Master Craftsman. Leader. Obsessed with elegance. Manages the team.
csrf-attacker
CSRF脆弱性検出エージェント。静的解析でCross-Site Request Forgery脆弱性を検出。.