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/metaspartan/cybara/systematic-debuggingnpx skills add metaspartan/cybara --skill systematic-debugginggit clone --depth 1 https://github.com/metaspartan/cybaraWrote 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/metaspartan/cybara/systematic-debugging)<a href="https://agentmods.dev/skills/metaspartan/cybara/systematic-debugging"><img src="https://agentmods.dev/badge/skills/metaspartan/cybara/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 | $0.00040 | $0.00430 |
| Opus 5 | $0.00020 | $0.00215 |
| Sonnet 5 | $0.00008 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
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 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
Systematic Debugging
A disciplined loop that finds the true root cause before changing code. Skipping it is the #1 cause of "fixes" that regress or don't hold.
The loop
- Reproduce reliably. Get a minimal, repeatable repro (command, input, test). If you can't reproduce it, say so and gather more info before touching code.
- Read the error fully. Capture the exact message, stack trace, and the line it points to. Don't guess from a summary.
- Isolate. Narrow the trigger: which input, which code path, which environment/version? Binary-search with logs or by disabling code.
- Form ONE hypothesis about the root cause. State it explicitly: "I think X happens because Y."
- Verify the hypothesis with the cheapest probe: a log, a print, a test, a debugger breakpoint (
lsp_diagnostics,execwith a tiny script). Confirm before fixing. - Fix the root cause, not the symptom. The fix should make the repro pass AND not break related cases.
- Add a regression test that captures the repro, so it can't come back.
- Re-run the full affected test suite, not just the one case.
Anti-patterns to avoid
- Changing multiple things at once → you won't know which fixed it.
- "Fixing" by catching/swallowing the error.
- Editing code based on a guess without confirming the hypothesis.
- Declaring fixed without re-running the repro.
When stuck
- Re-read the original repro; assumptions drift.
- Search code (
grep) and the issue for similar symptoms. - Check recent changes (
git log,git diff) — regressions usually track recent edits. - Form a NEW hypothesis; don't keep retesting the same one.
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 · 34 lines · 40 tokens per session scan A 7e2468e80cc4
systematic-debugging is a skill published in the GitHub repository metaspartan/cybara (25 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 430 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
superpowers-test-driven-development
Skill "superpowers-test-driven-development" from KornLabs/truss, covering test-driven development (tdd), when to use, the iron law, red-green-refactor and red - write failing test.
08-debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
hatch3r-bug-fix
Step-by-step bug fix workflow. Diagnose root cause, implement minimal fix, write regression test. Use when fixing bugs, working on bug report issues, or when the user mentions a bug.
aidd-tdd
Systematic test-driven development with proper test isolation. Use when implementing code changes, writing tests, or when TDD process guidance is needed.
aidd-fix
Fix a bug or implement review feedback following the AIDD fix process. Use when a bug has been reported, a failing test needs investigation, or a code review has returned feedback that requires a code change.