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/TheLobbi/claudeWrote 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/commands/thelobbi/claude/cc-troubleshoot)<a href="https://agentmods.dev/commands/thelobbi/claude/cc-troubleshoot"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/cc-troubleshoot/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/commands/thelobbi/claude/cc-troubleshoot"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/cc-troubleshoot.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.00000 | $0.00446 |
| Opus 5 | $0.00000 | $0.00223 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
cc-troubleshoot 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 9d 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
/cc-troubleshoot — Claude Code Issue Diagnostics
Diagnose and fix Claude Code setup and runtime issues.
Usage
/cc-troubleshoot [issue-type]
Issue Types
/cc-troubleshoot # Run full diagnostics
/cc-troubleshoot auth # Authentication issues
/cc-troubleshoot mcp # MCP server issues
/cc-troubleshoot hooks # Hook issues
/cc-troubleshoot config # Configuration issues
/cc-troubleshoot permissions # Permission issues
/cc-troubleshoot performance # Performance issues
/cc-troubleshoot install # Installation issues
/cc-troubleshoot plugins # Plugin issues
Implementation
When invoked, activate the claude-code-debugger agent to run systematic diagnostics:
Full Diagnostics (no issue-type)
- Environment check (Node, npm, Claude Code version)
- Authentication check (API key, provider)
- Configuration validation (settings.json, .mcp.json, CLAUDE.md)
- MCP server status
- Hook validation
- Plugin validation
- Check lessons-learned for known issues
- Report all findings with severity
Targeted Diagnostics (with issue-type)
Focus only on the specified area with deeper analysis.
Output Format
=== Claude Code Diagnostics ===
[PASS] Node.js v20.11.0
[PASS] Claude Code v1.2.3
[PASS] API Key configured (54 chars)
[PASS] settings.json valid
[WARN] 3 unresolved issues in lessons-learned.md
[FAIL] MCP server "postgres" not responding
[FAIL] Hook script .claude/hooks/guard.sh not executable
=== Recommended Fixes ===
1. Fix MCP server: Check DATABASE_URL env var
2. Fix hook: chmod +x .claude/hooks/guard.sh
Auto-Fix
When possible, offer to automatically fix issues:
- Make scripts executable
- Fix JSON syntax errors
- Set missing env vars (prompt for values)
- Install missing dependencies
- Clear corrupted cache
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.
- 9d ago First seen · 65 lines · 0 tokens per session scan A 7bedd36bae95
cc-troubleshoot is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 446 tokens. 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.