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 davesheffer/hunch --skill fixgit 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/skills/davesheffer/hunch/fix)<a href="https://agentmods.dev/skills/davesheffer/hunch/fix"><img src="https://agentmods.dev/badge/skills/davesheffer/hunch/fix/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/davesheffer/hunch/fix"><img src="https://agentmods.dev/badge/skills/davesheffer/hunch/fix.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.00017 | $0.00174 |
| Opus 5.5 | $0.00007 | $0.00070 |
| Sonnet 5.5 | $0.00003 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
fix 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.
What it actually says
We are fixing: $ARGUMENTS
Follow the Hunch-grounded workflow — do NOT skip the memory lookups:
hunch_bug_lineage("$ARGUMENTS")— has this class of bug happened before? what was the root cause and the fix?- Identify the suspect symbol/file, then
hunch_get_dependents(<symbol>)to learn the blast radius. hunch_check_constraints(<scope>)— list invariants you must preserve.- Propose a fix that honors past root causes AND constraints. Apply it and run the tests.
- If the fix encodes a non-trivial choice,
hunch_record_decision(...)so the next session is grounded in 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.
- 1mo ago First seen · 12 lines · 17 tokens per session scan A 6d87a3d6e1fe
fix is a skill published in the GitHub repository davesheffer/hunch (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 174 once invoked, about $0.0001 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
bug-report-reproduce
Reproduce a user, customer, or support-reported problem with synthetic data, prove the cause with a temporary test, record a narrated click-through walkthrough of the symptom, and report what was and was not proven. Use when the user links a bug report, support thread, or ticket and asks to reproduce it, find the…
changes-explain
Explain a pull request, commit range, branch, or local diff from a system-design perspective. Use for practical understanding of changed behavior, boundaries, flow, ownership, operations, risks, and verification rather than defect review.
debug-issue
Systematically debug issues using graph-powered code navigation.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.