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 Bbeierle12/Skill-MCP-Claude --skill systematic-debugginggit clone --depth 1 https://github.com/Bbeierle12/Skill-MCP-ClaudeWrote 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/bbeierle12/skill-mcp-claude/systematic-debugging)<a href="https://agentmods.dev/skills/bbeierle12/skill-mcp-claude/systematic-debugging"><img src="https://agentmods.dev/badge/skills/bbeierle12/skill-mcp-claude/systematic-debugging.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.00032 | $0.00793 |
| Opus 5 | $0.00016 | $0.00396 |
| Sonnet 5 | $0.00006 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00079 |
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 3d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging
Core Principle
Don't guess. Investigate systematically.
After 3 failed fix attempts, STOP and question the architecture.
Phase 1: Understand the Problem
Gather Information
- What is the expected behavior?
- What is the actual behavior?
- When did it start failing?
- What changed recently?
Reproduce Consistently
- Create minimal reproduction case
- Document exact steps to reproduce
- Identify if it's deterministic or intermittent
Check the Obvious First
- Is it plugged in? (Services running, dependencies installed)
- Are you in the right environment?
- Did you save the file?
- Is the cache cleared?
Phase 2: Root Cause Tracing
Backward Tracing Technique
- Where does the bad value appear?
- What called this with the bad value?
- Keep tracing up until you find the source
- Fix at source, not at symptom
Find Working Examples
- Locate similar working code in same codebase
- What works that's similar to what's broken?
- Compare against references
Identify Differences
- What's different between working and broken?
- List every difference, however small
- Don't assume "that can't matter"
Phase 3: Form Hypothesis
Scientific Method
- Form a SINGLE hypothesis
- Predict what you'd see if hypothesis is true
- Design a test to verify
- Run the test
- If wrong, form new hypothesis based on new data
Don't Multi-Hypothesis
- One hypothesis at a time
- Test it completely before moving on
- Don't mix debugging approaches
Phase 4: Implement Fix
Write Failing Test First
- Test that reproduces the bug
- Test should fail before fix
- Test should pass after fix
Single Fix at a Time
- ONE change only
- No "while I'm here" improvements
- No bundled refactoring
Verify Completely
- Original test passes
- No other tests broken
- Issue actually resolved
- Edge cases covered
Phase 5: If Fix Doesn't Work
After Each Failed Attempt
- STOP
- Count: How many fixes have you tried?
- If < 3: Return to Phase 1, re-analyze with new information
- If ≥ 3: STOP and question the architecture
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.
- 3d ago First seen · 140 lines · 32 tokens per session scan A 622e382df549
systematic-debugging is a skill published in the GitHub repository Bbeierle12/Skill-MCP-Claude (8 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 793 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-09-03.
Other skills, from other repositories
flask-werkzeug-attack
Exploit Flask/Werkzeug debugger exposure for traceback and SECRET leaks.
developing-with-streamlit
Use for ALL Streamlit tasks: creating, editing, debugging, beautifying, styling, theming, optimizing, or deploying Streamlit apps. Also custom components, st.components.v2, HTML/JS/CSS work. Discovers and loads version-matched reference docs from the user's installed Streamlit (>=1.57). Triggers: streamlit, st.…
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
eve
Build durable backend AI agents with the eve framework. Use when creating, editing, or debugging an eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals.
plugin-architecture-patterns
Design, implement, or diagnose Xberg plugin traits, typed registries, priority collisions, lifecycle, native extractors, and Alef-generated Python plugin bridges. Load for plugin-system work, not ordinary extractor parsing.
test-corpus
The testdocuments submodule is a bucket-fetched fixture corpus that is not committed. This skill covers readtestfixture, missing fixtures, valid A/B controls, and submodule push order. Load before running Rust tests on a fresh clone, setting up an A/B control, adding a fixture-backed test, or diagnosing…