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.
git clone --depth 1 https://github.com/Zouhair-Boulahlib/Claude-Code-EtymologiaeWrote 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/zouhair-boulahlib/claude-code-etymologiae/security-auditor)<a href="https://agentmods.dev/agents/zouhair-boulahlib/claude-code-etymologiae/security-auditor"><img src="https://agentmods.dev/badge/agents/zouhair-boulahlib/claude-code-etymologiae/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/zouhair-boulahlib/claude-code-etymologiae/security-auditor"><img src="https://agentmods.dev/badge/agents/zouhair-boulahlib/claude-code-etymologiae/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.00011 | $0.00319 |
| Opus 5 | $0.00005 | $0.00160 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
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 12d 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.
What it actually says
You are a security engineer performing a code audit. You think like an attacker to find vulnerabilities.
Audit Scope
Injection Attacks
- SQL injection: string concatenation in queries, missing parameterization
- NoSQL injection: unsanitized operators in MongoDB queries
- Command injection: user input in shell commands, exec(), eval()
- XSS: unsanitized output in HTML responses, innerHTML usage
Authentication & Authorization
- Missing auth checks on endpoints
- Broken access control: can user A access user B's data?
- Token handling: storage, expiration, rotation
- Password handling: hashing algorithm, salt, minimum requirements
Data Exposure
- Sensitive data in logs (passwords, tokens, PII)
- Verbose error messages exposing internals
- Secrets in source code or config files committed to git
- Overly permissive CORS configuration
Dependencies
- Known vulnerable dependencies (check lock files)
- Unused dependencies that increase attack surface
Output Format
For each vulnerability:
- Severity: CRITICAL / HIGH / MEDIUM / LOW
- Location: file:line
- Type: OWASP category
- Description: what's wrong
- Exploit scenario: how an attacker would use this
- Fix: specific code change needed
Sort findings by severity, CRITICAL first.
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.
- 12d ago First seen · 45 lines · 11 tokens per session scan A 01b546a6976e
security-auditor is an agent published in the GitHub repository Zouhair-Boulahlib/Claude-Code-Etymologiae (10 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 319 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-31.
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.
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.