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 HigorAlves/orc --skill systematic-debugginggit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/higoralves/orc/systematic-debugging)<a href="https://agentmods.dev/skills/higoralves/orc/systematic-debugging"><img src="https://agentmods.dev/badge/skills/higoralves/orc/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/higoralves/orc/systematic-debugging"><img src="https://agentmods.dev/badge/skills/higoralves/orc/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.00033 | $0.02524 |
| Opus 5.5 | $0.00013 | $0.01010 |
| Sonnet 5.5 | $0.00007 | $0.00505 |
| Haiku 4.5 | $0.00003 | $0.00252 |
Grade A, and why
systematic-debugging scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Phase 1 is done when you can name **one command** — a script path, a test invocation, a curl — that you have **already run at least once** (show the invocation and its output, redacted), and that is: How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
This is orc iron rule #4. If you haven't completed Phase 1, you cannot propose fixes. Use this discipline for ANY technical issue — test failures, production bugs, build failures, performance problems — and ESPECIALLY under time pressure: systematic is faster than guess-and-check thrashing. Simple bugs have root causes too.
When running under /orc:debug, the phases below map onto the command's resumable session: the diagnosis persists to .orc/<branch>/files/diagnosis.md and checkpoints let /orc:resume continue an interrupted investigation.
Before exploring the codebase, read the project's glossary (GLOSSARY.md if it exists) and ADRs in the area you're touching.
Redact
This skill has you show commands, outputs and captured artifacts. Redact every secret first: write <REDACTED> in its place. Build loops against env vars so the credential stays in the environment rather than in what you show. Captured artifacts carry auth headers — quote only the lines that carry the signal. If the redacted output is not enough to diagnose the bug, say so and ask the user.
Phase 1 — Build a feedback loop
This is the skill. Everything else is mechanical. If you have a tight pass/fail signal that goes red on this bug, you will find the cause — bisection, hypothesis-testing, and instrumentation all just consume it. If you don't have one, no amount of staring at code will save you.
Spend disproportionate effort here. Be aggressive. Be creative. Refuse to give up.
Ways to construct one — try in roughly this order
- Failing test at whatever seam reaches the bug — unit, integration, e2e.
- Curl / HTTP script against a running dev server.
- CLI invocation with a fixture input, diffing stdout against a known-good snapshot.
- Headless browser script (Playwright /
orc:agent-browser) — drives the UI, asserts on DOM/console/network. - Replay a captured trace. Save a real request / payload / event log to disk; replay it through the code path in isolation.
- Throwaway harness. A minimal subset of the system (one service, mocked deps) that exercises the bug path with a single call.
- Property / fuzz loop. If the bug is "sometimes wrong output", run 1000 random inputs and look for the failure mode.
- Bisection harness. If the bug appeared between two known states, automate "boot at state X, check, repeat" so you can
git bisect runit. - Differential loop. Same input through old vs new version (or two configs); diff outputs.
- HITL bash script. Last resort. If a human must click, drive them with
scripts/hitl-loop.template.shso the loop is still structured and its captured output feeds back to you.
What ships with it
6 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.
- 6d ago Changed · +5 lines · -18 tokens per session 55a6c3c7109d
- 1mo ago First seen · 149 lines · 51 tokens per session scan A b693c57ed56e
systematic-debugging is a skill published in the GitHub repository HigorAlves/orc (7 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 2,524 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
debug
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
parallax-core
Apply session-safe Parallax reasoning and verification to code changes.
fable-debug
Use when behavior contradicts expectation — a bug, an unexplained error, a failing test, output that looks wrong, a fix that didn't hold — or when you're about to retry the same category of fix a second time, or work keeps failing or stalling. Also when the user says "debug this", "why is this happening", or "still…
five-whys
Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
sandbox-unblock
Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change. Eleven checks that eliminate false positives, then a report template the person holding the settings can act on. On one measured day, six of eight reported blockers turned out to be false, all from the same handful of…