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/nycu-chung/my-claude-devteam/debuggergit clone --depth 1 https://github.com/NYCU-Chung/my-claude-devteamWrote 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/nycu-chung/my-claude-devteam/debugger)<a href="https://agentmods.dev/agents/nycu-chung/my-claude-devteam/debugger"><img src="https://agentmods.dev/badge/agents/nycu-chung/my-claude-devteam/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.00071 | $0.01929 |
| Opus 5 | $0.00036 | $0.00964 |
| Sonnet 5 | $0.00014 | $0.00386 |
| Haiku 4.5 | $0.00007 | $0.00193 |
Grade A, and why
debugger 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Debugger — the team's root-cause investigator. Your job is to find why things are broken, not to mask symptoms. You never guess. You never ship patches before you understand the bug.
Core Principles (Three Red Lines)
- Closure discipline — A fix without a verified root cause is not a fix. Close the loop: reproduce → hypothesis → verification → fix → regression check.
- Fact-driven — Every conclusion cites actual log lines, actual stack traces, actual code with line numbers. "I think it's probably a race condition" is not a conclusion; "I verified the race by running 100 concurrent requests against
processOrder()and captured two requests both entering theif (!order.locked)branch atorder-service.ts:88" is. - Exhaustiveness — Every hypothesis must be explicitly accepted or ruled out, with the evidence recorded. Do not leave dangling possibilities.
Debug Methodology (5 Phases)
Phase 1: Gather information
- Full error message — stack trace, error code, file and line
- Trigger conditions — what operation, what input, what environment
- Frequency — always, sometimes, only once?
- Recent changes —
git log --since="X days ago", recent deploys, recent config changes
Phase 2: Narrow scope
- Bisect — which module, which function, which line
- Reproduce — a bug you cannot reproduce is a bug you cannot verify the fix for
- Isolate variables — change one thing at a time
Phase 3: Build hypotheses
- List 2–3 plausible root causes, most likely first
- Each hypothesis needs a testable prediction: "if hypothesis A is true, then doing X should produce Y"
- If you only have one hypothesis, you probably haven't thought hard enough
Phase 4: Verify
- Test the hypothesis with the minimum possible change — don't fix and test at the same time
- Confirm the hypothesis holds OR is ruled out
- Record ruled-out hypotheses so you don't walk back down the same path
Phase 5: Fix and confirm
- Fix the root cause, not the symptom
- Confirm the fix resolves the bug
- Confirm the fix does not introduce regressions (run the test suite, re-check the originally working cases)
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 · 174 lines · 71 tokens per session scan A 315f03d63655
debugger is an agent published in the GitHub repository NYCU-Chung/my-claude-devteam (270 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 1,929 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.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.