systematic-debugging

systematic-debugging is a skill for Claude Code, Codex from BlackBeltTechnology/pi-agent-dashboard. It costs 86 tokens per session (1,666 once invoked), scanned A, original, MIT.

A step-by-step method for finding the proven root cause of an existing software bug before changing code.

In plain words
What is it for?
Use it for unclear test failures, flaky tests, regressions, CI-only problems, and fixes that have already failed once.
Why use it?
It prevents repeated guess-and-edit cycles that can hide the original problem, especially when failures are intermittent or differ between environments.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/blackbelttechnology/pi-agent-dashboard/systematic-debugging
Any agent
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill systematic-debugging
Clone the repo
git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for systematic-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/systematic-debugging.svg)](https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/systematic-debugging)
Your own site
<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/systematic-debugging"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/systematic-debugging.svg" alt="Measured on agentmods" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,666 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00086 $0.01666
Opus 5 $0.00043 $0.00833
Sonnet 5 $0.00017 $0.00333
Haiku 4.5 $0.00009 $0.00167

Measured 4d ago against content hash d978a8f081e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 4d 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.

packages/eng-disciplines/.pi/skills/systematic-debugging/SKILL.md · 129 lines

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

Overview

A bug is a gap between what the code does and what you believe it does. Guessing at fixes closes the gap by accident, if at all — and each blind edit adds a new variable that hides the real cause. Systematic debugging is the discipline of gathering evidence until the cause is known, then changing exactly one thing.

The failure mode this skill prevents: reading a stack trace, forming an instant theory, editing code to match the theory, re-running, and repeating. That loop feels like progress and usually is not — it mutates the system faster than it explains it.

When to Use

  • A test fails and the message doesn't immediately tell you why
  • Behaviour differs between environments ("works locally, fails in CI", "works in dev mode, not production")
  • A fix you already tried didn't work (you are now on attempt ≥ 2 — stop guessing)
  • An intermittent / flaky failure you can't reproduce on demand
  • A regression: something that worked now doesn't, and you don't know which change broke it

When NOT to use:

  • The cause is already obvious and proven (typo, off-by-one you can see, wrong constant)
  • You are building a new feature, not diagnosing existing behaviour
  • The "bug" is actually a missing requirement — that's a spec conversation, not a debug session

The Four Phases

Each phase has a success criterion. Do not advance until it is met. Skipping ahead is the whole antipattern.

Phase 1  ROOT CAUSE      gather evidence ─▶ criterion: you can state the cause in one sentence
   │                                        with evidence, not a guess
   ▼
Phase 2  PATTERN         is this cause elsewhere? ─▶ criterion: you've searched for sibling
   │                                                 instances of the same class of bug
   ▼
Phase 3  HYPOTHESIS      change ONE variable ─▶ criterion: a prediction that, if wrong,
   │                                            disproves your theory (a real test)
   ▼
Phase 4  IMPLEMENTATION  fix + regression test ─▶ criterion: a test that fails before the fix
                                                  and passes after

Read the full file on GitHub · 129 lines

Changes

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.

  1. 4d ago First seen · 129 lines · 86 tokens per session scan A d978a8f081e0

Subscribe to this mod's changes

systematic-debugging is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (271 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,666 once invoked, about $0.0004 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-08-30.