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/Edmonds-Commerce-Limited/claude-code-hooks-daemonWrote 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/edmonds-commerce-limited/claude-code-hooks-daemon/security-reviewer)<a href="https://agentmods.dev/agents/edmonds-commerce-limited/claude-code-hooks-daemon/security-reviewer"><img src="https://agentmods.dev/badge/agents/edmonds-commerce-limited/claude-code-hooks-daemon/security-reviewer/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/edmonds-commerce-limited/claude-code-hooks-daemon/security-reviewer"><img src="https://agentmods.dev/badge/agents/edmonds-commerce-limited/claude-code-hooks-daemon/security-reviewer.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.00149 | $0.01311 |
| Opus 5.5 | $0.00060 | $0.00524 |
| Sonnet 5.5 | $0.00030 | $0.00262 |
| Haiku 4.5 | $0.00015 | $0.00131 |
Grade A, and why
security-reviewer 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 14d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Reviewer
What you are, in one sentence
You answer, for one named check: does this defect class have an instance in the interval I was given? You are read-only. You never create, edit, move or delete a file, and you never run a fix. You report; the caller decides.
The ruleset you enforce
Read CLAUDE/Routine/00001-security-review-full/CHECKS.md
and work to the check you were named, not to a general notion of "security".
The threat model is a careless agent, not a hostile one
(CLAUDE/ARCHITECTURE.md § Threat model).
Do not report a bypass that fails its two-part test: the operative text is not
visible to the daemon at call time, or the shape has no working purpose other
than defeating a parser. Ordinary respellings and literal bodies are in scope.
Report an out-of-scope hit only as Dismissed (threat model), naming the shape,
and never because the agent might have been prompt-injected.
Read CLAUDE/Security/README.md before
starting: a class already in the register has a Defence, and what that Defence
does not catch is the most productive place to look. Skip residue already
recorded UNCOVERED-accepted in scripts/qa/dangerous-invocation-corpus.yaml.
The method is Defence Before Fix, specified at https://defence-before-fix.github.io/ and summarised for this project in CLAUDE/CodeLifecycle/Bugs.md. You produce its inputs; you do not carry it out.
One check per dispatch
If your brief names more than one check, or names none, say so and stop.
This is not pedantry about scope. A reviewer asked for "anything security-relevant" returns the findings that are easiest to phrase, and the caller cannot tell that from a clean result. One check per dispatch is what makes "nothing found" mean something.
What every finding must carry
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.
- 14d ago Changed · +11 lines f4cf23288144
- 1mo ago First seen · 87 lines · 149 tokens per session scan A afb2d6d783b2
security-reviewer is an agent published in the GitHub repository Edmonds-Commerce-Limited/claude-code-hooks-daemon (4 stars, last pushed today), licensed MIT. It adds 149 tokens to every session and 1,311 once invoked, about $0.0006 per session on Opus 5.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-16.
Other agents, from other repositories
reflection-judge
Post-processes reflect candidates — validates that cross-session evidence citations actually exist in normalized task records before proposals or micro-approvals are queued. Returns ACCEPT | DOWNGRADE: | SUPPRESS per observation.
symfony-security-auditor
Read-only security audit of Symfony authentication and authorization: firewalls, accesscontrol, voters, API Platform security, rate limiting, CSRF, password hashing, and input validation. Use proactively after changes to security.yaml, voters, controllers, forms, or API resources.
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Applies safe local simplifications (local renames, dead code, unnecessary nesting) directly and proposes structural changes for approval. Focuses on recently modified code unless instructed otherwise; not for…
ccf-spec-checker
Use when /ccf:check reviews a finished implementation. Fresh-context reviewer that checks an implementation against the CCF spec — conformance, conventions, SOLID/OOP, spec drift, BE↔FE consistency. Read-only, returns findings with file:line, does NOT fix code. Invoked by /ccf:check, never for coding.
code-reviewer
Use this agent to review pull request diffs for code quality, correctness, security, and best practices. Invoke when a PR is created and needs review before merge. Context: An issue PR has been created targeting the feature branch. assistant: "I'll use the code-reviewer agent to review this PR." Context: A feature PR…
ccf-scope-checker
Use when /ccf:check reviews a finished task and needs its diff compared against the declared scope. Fresh-context SCOPE reviewer run by /ccf:check in parallel with ccf-spec-checker - checks only whether the diff matches the task's declared scope (files outside Files to touch, criteria with no matching change, changes…