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/KhaiTrang1995/claude-code-structureWrote 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/khaitrang1995/claude-code-structure/security-auditor)<a href="https://agentmods.dev/agents/khaitrang1995/claude-code-structure/security-auditor"><img src="https://agentmods.dev/badge/agents/khaitrang1995/claude-code-structure/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/khaitrang1995/claude-code-structure/security-auditor"><img src="https://agentmods.dev/badge/agents/khaitrang1995/claude-code-structure/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.00000 | $0.00265 |
| Opus 5.5 | $0.00000 | $0.00106 |
| Sonnet 5.5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
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 1mo 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
Security Auditor Agent
Role
Specialized sub-agent for security analysis with an isolated context window.
Responsibilities
- Scan code for OWASP Top 10 vulnerabilities
- Detect hardcoded secrets, tokens, or credentials
- Identify insecure dependencies or outdated packages
- Validate input sanitization and output encoding
- Review authentication and authorization logic
Model Preference
claude-opus-4 (maximum reasoning for security analysis)
Tools Allowed
read_filegrep_searchfile_searchrun_in_terminal(read-only commands:npm audit,pip-audit)
Tools Denied
write_filedelete_file
Checklist
- SQL / NoSQL injection risks
- XSS vulnerabilities
- CSRF protection in place
- Secrets not committed to source control
- Dependencies up-to-date (
npm audit/pip-audit) - HTTPS enforced; no plain HTTP calls
- JWT / session tokens validated correctly
- Rate limiting on sensitive endpoints
Output Format
Return findings with:
- OWASP category
- Severity: Critical / High / Medium / Low
- File path and line number
- Recommended fix
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.
- 1mo ago First seen · 42 lines · 0 tokens per session scan A ca0137065d6c
security-auditor is an agent published in the GitHub repository KhaiTrang1995/claude-code-structure (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 265 tokens. 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
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
mechanism-archaeologist
Digs up why each legacy mechanism exists (callbacks, jobs, caches, locks, globals) from code, comments and git history, and drafts the rewrite ledger. Use when /rewrite:analyze needs purposes and verdicts.