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 PedroMosquera/squadai --skill systematic-debugginggit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/pedromosquera/squadai/systematic-debugging)<a href="https://agentmods.dev/skills/pedromosquera/squadai/systematic-debugging"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/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/pedromosquera/squadai/systematic-debugging"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/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.00015 | $0.00669 |
| Opus 5.5 | $0.00006 | $0.00268 |
| Sonnet 5.5 | $0.00003 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
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 7d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging Skill
Diagnose and fix failing tests using a structured 4-phase protocol. This skill is used by the Debugger when tests are failing and the cause is not immediately obvious.
The 4-Phase Protocol
Phase 1: REPRODUCE
-
Identify the failing test(s) exactly.
- Run the test suite and capture the exact failure output
- Note the assertion that failed and the expected vs actual values
- Record whether the failure is consistent or flaky
-
Create a minimal reproduction.
- Isolate the failing test from its suite
- Remove any unrelated setup or fixtures
- Confirm the minimal test still fails
-
Document what you know.
- When did the test start failing? (after which commit?)
- Does it fail on all machines or just some environments?
- Is the failure deterministic?
Phase 2: ISOLATE
-
Identify the failure boundary.
- Is the bug in the test itself (wrong assertion) or in the code under test?
- Add temporary logging or debug output at key points
- Use a binary search approach: remove half the code, check if still failing
-
Check common causes first.
- Off-by-one errors in loops
- Nil pointer dereference or missing initialization
- Incorrect error handling (error swallowed, wrong type)
- State leaking between tests (missing cleanup)
- Race condition (run with
-raceflag) - Wrong mock or stub behavior
-
Trace the data flow.
- Follow the input through each transformation
- Compare the actual intermediate values against expected values
- Find the first point where actual diverges from expected
Phase 3: FIX
-
Make the smallest targeted fix.
- Change ONLY what is necessary to fix the identified root cause
- Do not refactor or clean up while fixing
- If the fix requires a larger change, note it but keep it separate
-
Verify the fix addresses the root cause.
- Explain in a comment why the fix works
- Ensure the fix does not introduce new edge cases
-
Run the previously-failing test. It must now pass.
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.
- 7d ago Changed a257f1af37a8
- 1mo ago First seen · 96 lines · 15 tokens per session scan A d490a9584b8d
systematic-debugging is a skill published in the GitHub repository PedroMosquera/squadai (10 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 669 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-31.
Other skills, from other repositories
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…
hypothesis-testing
Applies the scientific method to debugging by helping users form specific, testable hypotheses, design targeted experiments, and systematically confirm or reject theories to find root causes. Use when a user says their code isn't working, they're getting an error, something broke, they want to troubleshoot a bug, or…
trace-and-isolate
Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code. Use when a bug is hard to locate, code is not working as expected, an error or crash appears with unclear cause, a regression was introduced between recent commits, or you need to narrow down which component…
root-cause-analysis
Performs systematic root cause analysis to identify the true source of bugs, errors, and unexpected behavior through structured investigation phases — not just treating symptoms. Use when a user reports a bug, crash, error, or broken behavior and needs to debug, troubleshoot, or investigate why something is not…
am-agent-code-debugger
Systematically identify, diagnose, and resolve bugs using advanced debugging techniques. Specializes in root cause analysis and complex issue resolution. Use PROACTIVELY for troubleshooting and bug investigation.
senior-developer-post-test-cleanup
Kill processes started for testing or demos.