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/mnzralee/claude-multi-agent-architecture/systematic-debuggingnpx skills add mnzralee/claude-multi-agent-architecture --skill systematic-debugginggit clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architectureWrote 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/mnzralee/claude-multi-agent-architecture/systematic-debugging)<a href="https://agentmods.dev/skills/mnzralee/claude-multi-agent-architecture/systematic-debugging"><img src="https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/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.1 | $0.00023 | $0.01382 |
| Opus 5 | $0.00012 | $0.00691 |
| Sonnet 5 | $0.00005 | $0.00276 |
| Haiku 4.5 | $0.00002 | $0.00138 |
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 5d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging Skill
A structured approach to debugging that ensures thorough diagnosis before attempting fixes. The discipline is stack-agnostic and applies equally to TypeScript/Node, Python, Go, or any other language and runtime.
When to Use This Skill
Use this skill when:
- An implementation agent fails with an error
- Tests are failing unexpectedly
- Runtime behavior does not match expectations
- Build or compilation errors occur
The Debugging Protocol
Phase 1: Error Capture
DO NOT attempt to fix anything until you understand:
## Error Analysis
### Exact Error
[paste exact error message]
### Error Location
- File: [path/to/file]
- Line: [line number]
- Function: [function name]
### Error Type
- [ ] Compilation error
- [ ] Runtime error
- [ ] Test failure
- [ ] Build failure
- [ ] Infrastructure error
### Trigger
What action caused this error?
Phase 2: Context Gathering
Before diagnosing, gather context:
# Recent changes
git log --oneline -10
# Changes in affected file
git diff HEAD~5 -- [file_path]
# Related files
grep -r "[error_pattern]" --include="*.ts"
Phase 3: Root Cause Analysis
Use the "5 Whys" technique:
## Root Cause Analysis
1. **Why did the error occur?**
[Direct cause, e.g., "Property 'x' does not exist on type 'Y'"]
2. **Why does property 'x' not exist?**
[e.g., "The type definition was changed"]
3. **Why was the type definition changed?**
[e.g., "A schema migration removed the field"]
4. **Why wasn't the code updated?**
[e.g., "The dependent service wasn't identified"]
5. **Why wasn't it identified?**
[ROOT CAUSE, e.g., "No automated dependency check"]
Phase 4: Impact Assessment
## Impact Assessment
### Direct Impact
- [File/component directly affected]
### Cascade Impact
- [Other components that depend on the affected code]
### Test Impact
- [Tests that will fail due to this issue]
### User Impact
- [How this affects end users if deployed]
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.
- 5d ago First seen · 261 lines · 23 tokens per session scan A a14cc8e447ab
systematic-debugging is a skill published in the GitHub repository mnzralee/claude-multi-agent-architecture (5 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,382 once invoked, about $0.0001 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-31.
Other skills, from other repositories
coordinate-agents
Route Codex-native multi-agent orchestration in a Git repository through a local-first, recoverable Agent Bus. Use for role-based planning, task execution, review, recovery, adapters, and human-gated release workflows. The plugin supports Codex CLI, Google Antigravity CLI, Claude, and other configured coding agents.…
coordinate-task
Run a Coordinate Agents Task from requirement clarification through planning, implementation, review, and the human release gate. Hide Agent Bus transport details behind the durable Task API.
coordinate-setup
Discover coding CLIs on the current computer and configure a Coordinate Agents implementation agent. Use for setup, executable checks, registered agents, user-level configuration, and project-over-user precedence.
coordinate-recover
Diagnose and safely resume Coordinate Agents Tasks after executable failure, non-zero exit, timeout, stale claim, processing message, or Implementer ERROR. Recovery is explicit and never an automatic retry loop.
coordinate-review
Review a Coordinate Agents implementation as the Codex Reviewer. Verify the real commit, diff, tests, validation evidence, and specification without modifying the Implementer's product code.
code-quality
Use this skill when writing, refactoring, or reviewing code to ensure SOLID principles, clean architecture, DRY deduplication, and anti-overengineering simplification.