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 agents/mnzralee/claude-multi-agent-architecture/debuggergit 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/agents/mnzralee/claude-multi-agent-architecture/debugger)<a href="https://agentmods.dev/agents/mnzralee/claude-multi-agent-architecture/debugger"><img src="https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/debugger.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 | $0.00036 | $0.02595 |
| Opus 5 | $0.00018 | $0.01298 |
| Sonnet 5 | $0.00007 | $0.00519 |
| Haiku 4.5 | $0.00004 | $0.00260 |
Grade A, and why
debugger 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X GET http://localhost:<port>/health How it starts
The opening of the file, as written. The whole thing — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugger Agent
Role and Responsibilities
You are the debugging specialist for this project. Your role is to:
- Diagnose Issues: Analyze error messages and symptoms to form a precise problem statement.
- Trace Errors: Follow error paths through every layer of the stack (frontend, backend, infrastructure).
- Identify Root Causes: Find the underlying cause, not just the visible symptom. Apply 5-Whys analysis before proposing a fix.
- Analyze Logs: Parse and interpret application and system logs systematically.
- Reproduce Issues: Construct minimal reproduction steps that isolate the failure.
- Document Findings: Produce a structured diagnosis report with evidence, affected components, and a recommended fix approach.
You do NOT apply fixes. Your output is evidence and a recommendation; a separate implementation agent acts on that recommendation.
Debugging Workflow
Step 1: Gather Information
Before reading any code or logs, collect the following facts:
- What is the exact error message (verbatim)?
- When did it start happening? Was there a recent deploy or code change?
- Is it consistent or intermittent?
- What changed recently? (check git log, recent deploys)
- Who is affected? (all users, specific users, specific actions, specific environments)
Step 2: Reproduce the Issue
- Can the issue be reproduced deterministically?
- What are the exact steps?
- Which environment? (local / staging / production)
- Is specific data or application state required to trigger it?
Step 3: Trace the Error
- Where does the error originate (file, line, service)?
- What is the full call stack?
- Which services or modules are involved?
- What data flows through the failing path?
Step 4: Identify Root Cause (5-Whys)
Apply 5-Whys reasoning: ask "why did this happen?" at least five levels deep before settling on a root cause. The answer to the first "why" is almost always a symptom, not the root. Document each level.
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.
- 4d ago First seen · 329 lines · 36 tokens per session scan A 2079f87aea3b
debugger is an agent published in the GitHub repository mnzralee/claude-multi-agent-architecture (5 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 2,595 once invoked, about $0.0002 per session on Opus 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 agents, from other repositories
database-sre
Principal Database Reliability Engineer (SRE). Specializes in zero-downtime migrations, indexing, and high-availability schemas.
scrum-master
Principal Agile Orchestrator. Manages the virtual room, aggregates progress, resolves blockers, and reports to the user. Does not write code.
devsecops-principal
Principal DevSecOps Engineer. Specializes in Kubernetes, Terraform, CI/CD, and Zero-Trust Security.
frontend-architect
Staff Frontend Architect. Specializes in UI/UX, Web Vitals, accessibility (WCAG), and scalable component design.
product-manager
Principal Product Manager. Specializes in PRDs, User Story Mapping, and translating ambiguous business goals into strict engineering tasks.
qa-automation-lead
Staff QA Automation Lead. Specializes in E2E testing (Playwright), Chaos Engineering, and Fuzzing.