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 yeaight7/agent-powerups --skill bug-huntgit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/bug-hunt)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/bug-hunt"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/bug-hunt/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/yeaight7/agent-powerups/bug-hunt"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/bug-hunt.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.00022 | $0.00366 |
| Opus 5.5 | $0.00009 | $0.00146 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
bug-hunt 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
Purpose
Locate and fix the root cause of a bug with minimal scope. A correct fix beats a fast guess.
When to Use
- A specific, reproducible bug needs fixing.
- A test is failing and the cause is unclear.
- An unexpected behavior needs a targeted fix.
For complex, persistent, or multi-component bugs, use systematic-debugging instead.
Inputs
- Bug description or reproduction steps.
- Relevant error messages or stack traces.
- Access to the codebase and test suite.
Workflow
- Reproduce — Trigger the bug reliably before writing any code.
- Identify — Find the true failing layer, not just the first place the error surfaces.
- Fix — Apply the minimal change at the root cause.
- Test — Add or update a focused test that would have caught this bug.
Output
Root cause: <what caused the bug>
Fix: <what was changed and where>
Verification: <how the fix was confirmed>
Residual risk: <any edge cases not covered>
Verification
- Bug reproduced before fix was written
- Root cause identified (not just symptom location)
- Fix is minimal — no unrelated changes bundled in
- Test added or updated to prevent regression
Failure Modes
- Fixing the symptom — Error location ≠ root cause. Trace backward until the origin is found.
- Skipping reproduction — Fixes written without a reliable reproduction often miss the actual bug.
- Missing test — Without a regression test, the same bug is likely to return.
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 · 52 lines · 22 tokens per session scan A b8f821e2ace5
bug-hunt is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 22 tokens to every session and 366 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-09-14.
Other skills, from other repositories
ai-discover
Read-only discovery step of the auto-improvement loop. One bounded agent turn per cycle reads the focus files (Read/Grep/Glob only, no shell, no subagents) and replies with a JSON array of testable surfaces {file, line, symbol, rule, message, hypothesis}; the spine authors fixes and verifies them. Discovery only — no…
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
simplify-code
Sequential 3-lens cleanup of recent code changes.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol.
python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).