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 skills/zeikar/hyperclaude/hyper-debugnpx skills add zeikar/hyperclaude --skill hyper-debuggit clone --depth 1 https://github.com/zeikar/hyperclaudeWhat 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.00046 | $0.00453 |
| Opus 5 | $0.00023 | $0.00227 |
| Sonnet 5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
hyper-debug 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 yesterday.
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
hyper-debug
Debugging discipline tailored to this author's preferences.
Skip when
- You already know the exact line and exact fix (typo, missing import, obvious null check). Just fix it.
- The "bug" is a one-character correction that doesn't merit a hypothesis.
If you catch yourself rationalizing ("the cause is probably X, let me just try…") — that's hypothesis stacking. Run the cycle.
The cycle
- Reproduce. Smallest possible repro. If you can't reproduce, you can't debug.
- State the expected vs actual. Two sentences. "I expected X. I got Y."
- Hypothesize one cause. One. Not five. Pick the most likely.
- Predict what would prove the hypothesis right or wrong before running anything. "If hypothesis is correct, X should happen."
- Run the experiment. Compare to prediction.
- If wrong, hypothesize again. New hypothesis. Don't stack them.
- Once cause is confirmed, write a failing test that captures the bug before fixing — so it doesn't regress silently later.
- Fix. Run. Commit.
Anti-patterns
- Hypothesis stacking — trying five "fixes" at once and not knowing which one worked.
- Skipping the regression test — "the fix is obvious, no test needed." Write the test.
- Logging-only debugging — endless
console.logwithout forming hypotheses. Logs serve a hypothesis, not the other way around. - Reading code top-to-bottom — start at the failing assertion and walk backward, not forward.
When to escalate
If after 2-3 hypotheses you still don't know the cause, stop iterating. Re-read the error message slowly, check if your repro is actually exercising the buggy code, or take a 5-minute break — you have a wrong assumption somewhere upstream.
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.
- yesterday First seen · 38 lines · 46 tokens per session scan A bfb685405363
hyper-debug is a skill published in the GitHub repository zeikar/hyperclaude (3 stars, last pushed 14d ago), licensed MIT. It adds 46 tokens to every session and 453 once invoked, about $0.0002 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 skills, from other repositories
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.
workflow
Professional AI programming assistant with structured workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) for developers.
golden-rss
Use when testing the rss golden build.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
golden-chat-topics
Use when testing the goldenchattopics golden build.