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 bhaumikmaan/claude-code-master-skills --skill systematic-debugginggit clone --depth 1 https://github.com/bhaumikmaan/claude-code-master-skillsWrote 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/bhaumikmaan/claude-code-master-skills/systematic-debugging)<a href="https://agentmods.dev/skills/bhaumikmaan/claude-code-master-skills/systematic-debugging"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/systematic-debugging/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/bhaumikmaan/claude-code-master-skills/systematic-debugging"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/systematic-debugging.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.00052 | $0.01486 |
| Opus 5.5 | $0.00021 | $0.00594 |
| Sonnet 5.5 | $0.00010 | $0.00297 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
systematic-debugging 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging
CRITICAL: This is a diagnostic skill. Investigate first, fix second. Don't guess — gather evidence.
Diagnostic Mindset
- Don't report when healthy. If everything looks fine, say so directly — don't manufacture issues.
- Don't kill or signal processes unless explicitly asked. This is diagnostic only.
- Read errors before guessing causes. The error message is the first evidence.
- Reproduce before fixing. A fix you can't verify is a guess.
Symptom-to-Hypothesis Map
Start here. Match the symptom to candidate hypotheses, then investigate:
| Symptom | Likely Hypotheses | First Investigation |
|---|---|---|
| High CPU (≥90% sustained) | Infinite loop, runaway regex, tight polling | Sample twice 1-2s apart to confirm sustained; check stack/profile |
| Process in D state (uninterruptible sleep) | I/O hang, disk full, NFS stall, lock contention | Check dmesg, disk usage, mount status |
| Process in T state (stopped) | Accidental Ctrl+Z, debugger attached | Check parent process, fg to resume |
| Zombie process (Z state) | Parent not reaping children | Check parent PID, signal parent |
| High memory (≥4GB RSS) | Memory leak, unbounded cache, large dataset loaded | Check growth over time, heap snapshot if available |
| Slow response | N+1 queries, blocking I/O on hot path, missing index | Profile request, check DB query count and timing |
| Hung child process | Waiting for stdin, deadlock, network timeout | pgrep -lP <pid>, check child's full command line |
| Intermittent failure | Race condition, resource exhaustion, DNS flake | Check timing patterns, add logging, reproduce under load |
| Build failure | Dependency version mismatch, stale cache, missing env var | Clean build, check lock file, diff with working state |
| Test failure (flaky) | Shared state, timing dependency, order dependency | Run test in isolation, check setup/teardown, look for shared mutable state |
Investigation Steps
1. Gather Context
- Read the error message / stack trace carefully. Most errors tell you exactly what's wrong.
- Check recent changes:
git log --oneline -10andgit diff— was something just changed? - Read relevant log files. Use bounded reading: tail the last 50-100 lines, don't read the entire log.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 129 lines · 52 tokens per session scan A 2f0330125b0f
systematic-debugging is a skill published in the GitHub repository bhaumikmaan/claude-code-master-skills (3 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 1,486 once invoked, about $0.0002 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
code-review
Reviews code for bugs, security issues, and best practices.
diagnosing-bugs
A structured process for diagnosing difficult software bugs and performance slowdowns. It starts by creating a repeatable pass-or-fail check, such as a failing test, HTTP request, command, or browser script.
error-translator
A Chinese-language assistant that translates English programming errors and explains what they mean. It covers common errors from languages and frameworks including Python, JavaScript, TypeScript, Java, and others.
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.