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 orlando-japan/claude-code-setting --skill debugging-strategiesgit clone --depth 1 https://github.com/orlando-japan/claude-code-settingWrote 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/orlando-japan/claude-code-setting/debugging-strategies)<a href="https://agentmods.dev/skills/orlando-japan/claude-code-setting/debugging-strategies"><img src="https://agentmods.dev/badge/skills/orlando-japan/claude-code-setting/debugging-strategies.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.1 | $0.00037 | $0.00704 |
| Opus 5 | $0.00018 | $0.00352 |
| Sonnet 5 | $0.00007 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
debugging-strategies 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 6d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging strategies
The fastest debugger is one that doesn't guess. Every step should be driven by evidence, not hunches.
Phase 1 — Reproduce
If you can't reproduce, you can't debug. Before any hypothesis:
- Minimal reproduction: smallest input / sequence / env that triggers the bug.
- Deterministic: same inputs, same bug, every time. If it's intermittent, find the hidden non-determinism first (timing, order, state).
- Isolated: no other noise. Strip the scenario down.
If you can't make it reproduce, spend effort on reproduction tooling, not on fixing.
Phase 2 — Bisect
Once reproducible, narrow the search:
- Git bisect if the bug is new — what commit introduced it?
- Code bisect — comment out half the code path. Does the bug remain? Which half?
- Data bisect — half the input. Does the bug remain with the smaller input?
- Binary search in output — where does good data become bad data? Log at midpoints.
Each step halves the search space. Don't skip halves out of laziness.
Phase 3 — Hypothesis & test
State the hypothesis out loud: "I think X is happening because of Y."
Then ask: "What experiment distinguishes this from alternatives?"
- A test that passes if X, fails if not-X.
- A log line that proves which branch was taken.
- A breakpoint with a specific inspection.
Run the experiment. Update your belief. Repeat.
Phase 4 — Fix at the root, not the symptom
When you find a misbehaving line, ask: "why is this line wrong?" Trace upward:
- Is the input wrong? Why?
- Is the caller wrong?
- Is the caller's caller wrong?
Stop at the first cause that, if fixed, would prevent this class of bug, not just this instance.
Symptom patches (null-check the crash site, catch the error, retry the request) silence the bug without fixing it. Reserve them for "ship now, fix next week" — and actually do the fix next week.
Common traps
- Confirmation bias. You form a hypothesis and only look at data confirming it. Ask: "what would prove me wrong?"
- Changing two things at once. When multiple variables change simultaneously, you can't attribute the outcome. Change one, observe, then the next.
- Fixing what isn't broken. The bug is somewhere; it's probably not where you first looked. Prove the bug is where you think before patching.
- Stopping at "it works now." If you don't know why it works, you don't know why it'll break again.
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.
- 6d ago First seen · 71 lines · 37 tokens per session scan A 312088e74ec6
debugging-strategies is a skill published in the GitHub repository orlando-japan/claude-code-setting (2 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 704 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
fixing
Diagnose why a PR's CI failed — compare the CI definition against the sandbox, classify the failure, and make the minimal repair. Use when a PR is red and you must work out why before changing anything.
Bug Root Cause Analyzer
Systematically diagnoses bugs by tracing execution flow and identifying root causes vs symptoms.
bug-diagnosis
Use this skill to systematically diagnose the root cause of a bug before attempting a fix. Activates when a bug is reported, a test is failing, or unexpected behavior is observed. Prevents guess-and-check debugging that introduces additional bugs while chasing symptoms.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
trulens-diagnosis
Diagnose low evaluation scores and generate actionable improvement recommendations.
trace
Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…