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 agentmods add commands/davesheffer/hunch/hunch-whygit clone --depth 1 https://github.com/davesheffer/hunchWrote 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/commands/davesheffer/hunch/hunch-why)<a href="https://agentmods.dev/commands/davesheffer/hunch/hunch-why"><img src="https://agentmods.dev/badge/commands/davesheffer/hunch/hunch-why.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 | $0.00015 | $0.00140 |
| Opus 5 | $0.00008 | $0.00070 |
| Sonnet 5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
hunch-why 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 4d 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
Use the hunch_why MCP tool on $ARGUMENTS (a file path or symbol name).
Then summarize, with citations:
- the decisions that shaped it (id + rationale),
- the constraints that must not break,
- the bug history behind it (root causes).
Cite record ids and their provenance/confidence. If Hunch returns nothing,
say so plainly and suggest running hunch index or hunch backfill.
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.
- 4d ago First seen · 15 lines · 15 tokens per session scan A 39db8f4f5c1d
hunch-why is a command published in the GitHub repository davesheffer/hunch (9 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 140 once invoked, about $0.0001 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 commands, from other repositories
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.
go-review
Go code review for idiomatic patterns.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
fix
Universal debugging and fix application with semantic code analysis.
harness-adopt
Apply Harness Starter Kit to the current target repository with the prompt-first adoption workflow.
test
Run all PandaFilter verification steps in order. Stop and report on first failure. This is the required pre-commit gate.