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 ssube/conclave --skill systematic-debugginggit clone --depth 1 https://github.com/ssube/conclaveWrote 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/ssube/conclave/systematic-debugging)<a href="https://agentmods.dev/skills/ssube/conclave/systematic-debugging"><img src="https://agentmods.dev/badge/skills/ssube/conclave/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/ssube/conclave/systematic-debugging"><img src="https://agentmods.dev/badge/skills/ssube/conclave/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.00055 | $0.01127 |
| Opus 5.5 | $0.00022 | $0.00451 |
| Sonnet 5.5 | $0.00011 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00113 |
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 1mo 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.
| API 401/403 | Token expired or revoked | Check env var, try manual curl | How it starts
The opening of the file, as written. The whole thing — 133 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.
Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
Adapted from obra/superpowers.
When to Use
Use for ANY technical issue:
- Playwright posting failures (session expired, element not found)
- API errors (rate limits, auth failures, unexpected responses)
- ComfyUI generation failures (model not found, OOM, workflow errors)
- Infrastructure issues (ChromaDB down, SQLite locked, disk full)
- Build/deploy failures (Hugo, Cloudflare)
- Data anomalies (metrics that don't make sense)
Use 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
The Four Phases
Complete each phase before proceeding to the next.
Phase 1: Root Cause Investigation
BEFORE attempting ANY fix:
-
Read error messages carefully
- Full stack traces, not just the last line
- Error codes, HTTP status codes
- File paths and line numbers
- Don't skip warnings
-
Reproduce consistently
- Can you trigger it reliably?
- Same error every time, or intermittent?
- If intermittent → gather more data, don't guess
-
Check recent changes
git log --oneline -10- Were env vars changed? Sessions rotated? APIs updated?
- Did a platform deploy an update? (Search web if suspected)
-
Trace the data flow (for multi-component systems)
For EACH component boundary: - Log what enters the component - Log what exits the component - Verify environment/config at each layerExample: Playwright posting → Session cookie → HTTP request → Platform API Which layer fails?
Phase 2: Pattern Analysis
- Find working examples — Same skill worked yesterday? Different platform works?
- Compare — What's different between working and broken state?
- Check dependencies — Platform API changed? Cookie format different? Rate limit hit?
- Read the source — Don't guess what a script does. Read it.
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.
- 1mo ago First seen · 133 lines · 55 tokens per session scan A d3e72a23efef
systematic-debugging is a skill published in the GitHub repository ssube/conclave (2 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 1,127 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
test-fix
Diagnose and minimally fix a failing test, then re-run.
error-handler
Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead, timeout), error budgets/SLOs with burn rate alerts, and production incident triage. Use when user asks to implement error…
performance-profiler
Performance profiling and optimization for web apps — Core Web Vitals (LCP, INP, CLS), Lighthouse audits, bundle analysis, backend profiling (CPU, memory, DB queries), N+1 detection, caching strategies (Redis, CDN, HTTP), and performance budgets. Use when user asks to improve performance, run Lighthouse audit, profile…
code-coherence-review
Reviews code and plans for logic coherence, correctness, and structural integrity.
gsd-forensics
Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong.
hatch3r-incident-response
Handles production incidents with structured triage, mitigation, and post-mortem. Use when responding to production issues, outages, or security incidents.