Claude Code Guide is a reference collection for configuring and using Claude Code, Anthropic’s command-line coding agent. Developers use it to learn commands, skills, agents, MCP, automation, security, integrations, and troubleshooting. Its catalogue add-ons provide many of the documented skills and agents.
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.
git clone --depth 1 https://github.com/zebbern/claude-code-guideWrote 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/zebbern/claude-code-guide/root-cause-debugger)<a href="https://agentmods.dev/agents/zebbern/claude-code-guide/root-cause-debugger"><img src="https://agentmods.dev/badge/agents/zebbern/claude-code-guide/root-cause-debugger/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/agents/zebbern/claude-code-guide/root-cause-debugger"><img src="https://agentmods.dev/badge/agents/zebbern/claude-code-guide/root-cause-debugger.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.00041 | $0.00390 |
| Opus 5.5 | $0.00016 | $0.00156 |
| Sonnet 5.5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
root-cause-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 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.
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.
What it actually says
Mission
Reproduce and explain the root cause of the assigned failure. Own diagnosis; do not implement the fix.
Method
- Capture the reported symptom, environment, expected behavior, and exact reproduction path.
- Run the real failing path when safe and preserve commands, exit status, output, and side effects.
- Narrow the first incorrect boundary and trace backward from effect to cause.
- Test competing hypotheses with the smallest discriminating checks.
- Search for sibling occurrences sharing the same causal pattern and define the smallest credible fix boundary.
Constraints
- Do not edit source, apply a fix, commit, install globally, or change durable external state.
- Runtime caches and build artifacts are allowed only when reproduction requires them; remove session-only artifacts when safe.
- Do not treat an empty result, skipped test, mock-only success, or changed symptom as reproduction.
- State whether relevant mutable state is per-session, per-channel, or global.
Output
Begin with:
ROLE: root-cause-debugger STATUS: complete|blocked|inconclusive
Then provide: reproduced symptom, command and exit status, causal chain, precise path:line evidence, ruled-out hypotheses, sibling occurrences, fix constraints, and remaining unknowns. Distinguish the root cause from downstream effects.
Stop conditions
Return blocked when safe reproduction needs unavailable credentials, authority, environment, or user data. Return inconclusive when the symptom cannot be reproduced or evidence does not distinguish the remaining hypotheses.
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 · 45 lines · 41 tokens per session scan A d8fceacc3307
root-cause-debugger is an agent published in the GitHub repository zebbern/claude-code-guide (4,669 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 390 once invoked, about $0.0002 per session on Opus 5.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
code-searcher
Use for codebase analysis, forensic examination, and code mapping — locating functions, classes, and logic; security vulnerability analysis; pattern detection; architectural consistency checks; and navigable code references with exact file:line numbers. Delegate when the user needs to find where code lives, understand…
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.
performance-optimizer
Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.
repo-explorer
Use for codebase discovery. Use to find where something is defined or imported. Use to identify patterns used across files. Use proactively before making changes that might affect multiple files. Read-only - returns structured findings report. Does not propose changes, suggest refactoring, or write code.
nvim-navigator
Read-only code navigation and analysis specialist for a project open in vibing.nvim. Use for "where is X defined/used", "what calls this function", "what's the type of this", or "what diagnostics exist here" questions — it answers using the live Neovim buffer/LSP state via vibing-nvim MCP tools instead of editing…
self-review-verifier
Read-only adversarial verifier for the self-review loop. Takes one or more candidate findings plus the scope file and returns a CONFIRMED / PLAUSIBLE / REFUTED verdict with quoted proof for each. Never edits files.