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 DollarDill/beads-superpowers --skill systematic-debugginggit clone --depth 1 https://github.com/DollarDill/beads-superpowersWrote 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/dollardill/beads-superpowers/systematic-debugging)<a href="https://agentmods.dev/skills/dollardill/beads-superpowers/systematic-debugging"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/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/dollardill/beads-superpowers/systematic-debugging"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/systematic-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 100 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 101 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00021 | $0.03015 |
| Opus 5.5 | $0.00008 | $0.01206 |
| Sonnet 5.5 | $0.00004 | $0.00603 |
| Haiku 4.5 | $0.00002 | $0.00301 |
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 2mo 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging
Overview
Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
Violating the letter of this process is violating the spirit of debugging.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phase 1, you cannot propose fixes.
When to Use
Use for ANY technical issue:
- Test failures
- Bugs in production
- Unexpected behavior
- Performance problems
- Build failures
- Integration issues
Use this ESPECIALLY when:
- Under time pressure (emergencies make guessing tempting)
- "Just one quick fix" seems obvious
- You've already tried multiple fixes
- Previous fix didn't work
- You don't fully understand the issue
Don't skip when:
- Issue seems simple (simple bugs have root causes too)
- You're in a hurry (rushing guarantees rework)
- Manager wants it fixed NOW (systematic is faster than thrashing)
The Four Phases
You MUST complete each phase before proceeding to the next.
Phase 1: Root Cause Investigation
BEFORE attempting ANY fix:
-
Read Error Messages Carefully
- Don't skip past errors or warnings
- They often contain the exact solution
- Read stack traces completely
- Note line numbers, file paths, error codes
-
Reproduce Consistently
- Can you trigger it reliably?
- What are the exact steps?
- Does it happen every time?
- If not reproducible → gather more data, don't guess
-
Check Recent Changes
- What changed that could cause this?
- Git diff, recent commits
- New dependencies, config changes
- Environmental differences
- For workflow-level issues (blocked beads, stuck execution):
bd ready --explainshows dependency reasoning - Check the knowledge store for this symptom before investigating further:
bd memories <symptom-keywords>(prior root-cause/lesson memories) andbd list --label <topic> --status all(+bd search "<symptom>" --status allfor decision/design knowledge-beads; error strings are body terms: add--desc-contains "<error-string>"; >10 hits: narrow the query, never triage truncated titles). Then read — hits are pointers, not knowledge:bd show <ids>every plausibly-matching prior decision/design, andbd recall <key>every plausibly-matching memory (bd memoriesprints truncated previews) — full bodies, before investigating further. 0 relevant does not mean none exist — re-angle the query once before emittingKB check: none. EmitKB check: N hits, M read+ a one-line disposition each. If a prior root cause or decision already covers this, use it — don't re-debug something already understood.
What ships with it
5 files 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.
- 2mo ago First seen · 317 lines · 21 tokens per session scan A 78549f56e920
systematic-debugging is a skill published in the GitHub repository DollarDill/beads-superpowers (32 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 3,015 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-08-30.
systematic-debugging compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| systematic-debuggingDollarDill/beads-superpowers | Skill | 32 | 6d ago | MIT | A | 21 | Claude Code |
| beads-onboardseanmartinsmith/sms-public-mkt | Skill | 3 | 28d ago | MIT | A | 96 | Claude Code |
| systematic-debugging-codexmzored/superpowers-cc-to-codex | Skill | 7 | 6mo ago | MIT | A | 37 | Claude Code |
| release-itwondelai/skills | Skill | 2.6k | 4d ago | MIT | A | 131 | Claude Code, Codex |
| tidewave-integrationoliver-kriska/claude-elixir-phoenix | Skill | 574 | yesterday | MIT | A | 38 | Claude Code |
| anti-patternsavelikiy/great_cto | Skill | 112 | 2d ago | MIT | A | 59 | Claude Code |
| windows-compatsdsrss/code-graph-mcp | Skill | 91 | yesterday | MIT | A | 165 | Claude Code, Codex |