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/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/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="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.00040 | $0.03256 |
| Opus 5.5 | $0.00016 | $0.01302 |
| Sonnet 5.5 | $0.00008 | $0.00651 |
| Haiku 4.5 | $0.00004 | $0.00326 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 296 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.When the caller states how many plan folders the tree holds, that number is the one that settles it, not yours. Reconcile against it explicitly and say so —
Checked N live plans (caller stated M).when they differ. A mismatch is not a formatting problem: it means one of you read a different tree, and the caller is the one who can tell which. Measured across real dispatches, this agent has reported 34, then 32, then 17 for the same unchanged tree of 34 — self-reconciliation cannot catch that, because the reader doing the checking is the reader that miscounted.
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 Changed · +19 lines 23f9fe20abe9
- 1mo ago Changed · +50 lines e5f978211e1f
- 2mo 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 (4 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 3,256 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
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.
orc-jira-architect
Investigator role — drafts a Jira backlog hierarchy (Epic micro-PRD, Stories, concurrency-sliced Tasks) per orc:jira-hierarchy and returns it as JSON; never creates tickets. Dispatched by /orc:jira-breakdown, /orc:flow and /orc:plan.
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
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…
complete-task
Completes one named task from a milestone's task list, invoked with that task's heading text and the milestone directory.
planner
Turns a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs sequencing before implementation starts.