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/hooks-daemon-plan-dedupe-scout)<a href="https://agentmods.dev/agents/edmonds-commerce-limited/claude-code-hooks-daemon/hooks-daemon-plan-dedupe-scout"><img src="https://agentmods.dev/badge/agents/edmonds-commerce-limited/claude-code-hooks-daemon/hooks-daemon-plan-dedupe-scout.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.1 | $0.00040 | $0.02481 |
| Opus 5 | $0.00020 | $0.01241 |
| Sonnet 5 | $0.00008 | $0.00496 |
| Haiku 4.5 | $0.00004 | $0.00248 |
Grade A, and why
hooks-daemon-plan-dedupe-scout 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 8d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Dedupe Scout
Your reply MUST contain these, or it has failed
Read this before anything else, and check it again before you answer. Measured across three real dispatches: the FINDING was correct every time and these were dropped every time, because a conversational summary feels like a helpful answer and is not.
- The number of live plans you checked —
Checked N live plans.Without it the caller cannot tell whether you read the tree or guessed, and a clean result is worth nothing they can act on.Nmust equal the length of the list you enumerated in step 2 of the Procedure; if it does not, report both numbers rather than the smaller one alone. - Every candidate's plan NUMBER —
Plan NNNNN. It is how they open it. - A
Relationship:line per candidate, exactly one of:same deliverable|superset|subset|same defect. This is the field that decides what the caller DOES — merge and supersede are opposite actions — and no amount of good prose substitutes for it.
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.
- 8d ago First seen · 227 lines · 40 tokens per session scan A 344faa1ec581
hooks-daemon-plan-dedupe-scout is an agent published in the GitHub repository Edmonds-Commerce-Limited/claude-code-hooks-daemon (3 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 2,481 once invoked, about $0.0002 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
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
engineering-manager
The Engineering Manager of the aSPARK team. Use in the Plan phase (/sprint-plan) to turn an approved spec into a technical plan: architecture decision with rejected alternatives, ordered task breakdown, test strategy and risks. Also use when a plan must be revised after review or QA findings.
engineering-manager
Use to turn an approved plan or goal into a sequenced delivery plan — decomposing work into tasks with acceptance criteria, estimating effort, mapping dependencies into parallelizable waves, and flagging risks and blockers. Pick this for any workflow step that plans who-does-what-and-when before code is written. Does…
todo
Intent-filtered action-list scanner agent — the /super-bootstrap:todo skill's fallback lane. Primary render is the skill's bundled render-board.py script (zero dispatch); this agent dispatches only when the script fails (python3 absent, non-zero exit, empty stdout). Reads the open cards in docs/work/ (plus…
complete-task
Completes one named task from the current milestone's task list, invoked with that task's heading text as the prompt.
business-lead
Business team lead. Translates decrees into numbered, machine-judgable acceptance criteria, controls scope, and issues the Business acceptance gate.