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.
npx skills add Edmonds-Commerce-Limited/claude-code-hooks-daemon --skill docs-qagit 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/skills/edmonds-commerce-limited/claude-code-hooks-daemon/docs-qa)<a href="https://agentmods.dev/skills/edmonds-commerce-limited/claude-code-hooks-daemon/docs-qa"><img src="https://agentmods.dev/badge/skills/edmonds-commerce-limited/claude-code-hooks-daemon/docs-qa/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/skills/edmonds-commerce-limited/claude-code-hooks-daemon/docs-qa"><img src="https://agentmods.dev/badge/skills/edmonds-commerce-limited/claude-code-hooks-daemon/docs-qa.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.00057 | $0.00689 |
| Opus 5.5 | $0.00023 | $0.00276 |
| Sonnet 5.5 | $0.00011 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
docs-qa 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation QA
This skill is a shim. It carries no documentation body of its own — it
exists to dispatch the hooks-daemon-docs-qa agent, which does the real
work. Where the documentation subsystem is enabled, the ruleset it enforces
is written up in CLAUDE/DocumentationStrategy.md; the agent carries a
compressed model of the same rules for projects that have not enabled it.
What to do
Dispatch the hooks-daemon-docs-qa agent (Task tool,
subagent_type: "hooks-daemon-docs-qa") with:
- the scope the user asked for (a topic, a plan folder, or "the whole corpus" if unstated)
- a pointer to run the deterministic checks first:
hooks-daemon docs-qa --sweep --json - a pointer to the comment-block finder for its Decision-7 hunt:
hooks-daemon find-comment-blocks <source-root> --json
/docs-qa # full-corpus audit
/docs-qa CLAUDE/Plan/00284 # scoped to one plan folder's topic
The agent is read-only — it delivers findings inline, as its final
report, and never edits anything or writes a report file on its own
initiative. If you want the findings persisted (e.g. to
untracked/reports/), name that target explicitly when dispatching it.
Review its report and act on the findings yourself (or ask it to be
dispatched again after you have made changes, to re-verify).
If the agent is not deployed
hooks-daemon-docs-qa ships opt-in (agents.docs_qa.enabled: false by
default). If the Task dispatch fails because the agent is not found, tell
the user to enable it in .claude/hooks-daemon.yaml:
agents:
docs_qa:
enabled: true
then run hooks-daemon restart (or the next daemon upgrade/install run) to
deploy it into .claude/agents/hooks-daemon-docs-qa.md.
Bundled finder scripts
scripts/ bundles thin wrappers over the deterministic CLI, for a human or
the agent to run directly without recalling the exact daemon subcommand:
scripts/sweep.sh—hooks-daemon docs-qa --sweep --jsonscripts/find-comment-blocks.sh <path>...—hooks-daemon find-comment-blocks <path>... --json
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +2 lines be7ec65fccdc
- 1mo ago First seen · 65 lines · 57 tokens per session scan A e8f190360c37
docs-qa is a skill published in the GitHub repository Edmonds-Commerce-Limited/claude-code-hooks-daemon (4 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 689 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 skills, from other repositories
branch-recap
Takes stock of what a branch actually changed, before it gets pushed — works out the scope itself, then lays the change out group by group in one pass: files touched, what was done and why, how, and what deserves a second look, quoting code only where a remark needs it rather than reprinting the diffs. Closes on a…
audit-context
Measures where a project's Claude context is going before applying any of clean-context's levers. Reports what Glob discovers with and without ignore files applied, the twenty largest files in the repo and which are generated, the cumulative size of every CLAUDE.md loaded for this working directory, and how many MCP…
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read: filtered to what they would actually notice, one bullet per idea, plain language, no code vocabulary. Works out the scope itself across however many repositories sit in the working directory (a project can span several…
ignore-setup
Set up a project so Claude stops discovering lockfiles, generated code, minified assets and binaries on every search — a managed .ignore, the Glob setting that makes Glob obey it, and a short read-deny list for secrets. Use when someone asks for a .claudeignore, asks to exclude files from the context, says Claude…
plugin-commands
Commands for validating, testing, iterating on, and releasing plugins in this marketplace (claude-toolbelt) — plugin validate, watcher-parity check, eval, --plugin-dir dev loop, plugin tag. Use when validating a plugin before pushing, running skill evals, developing a plugin without touching the installed cache, or…
setup
One-command setup for usage-guard's real plan quota. Use this whenever the user runs /usage-guard:setup, asks to enable/activate/turn on the real 5-hour and weekly quota reading, asks to wire up the status line, or when /usage-guard:usage shows no "Real plan quota" block (only the weighted fallback). Detects the…