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/qazi0/claude-pluginsWrote 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/qazi0/claude-plugins/troubleshoot)<a href="https://agentmods.dev/commands/qazi0/claude-plugins/troubleshoot"><img src="https://agentmods.dev/badge/commands/qazi0/claude-plugins/troubleshoot.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.00025 | $0.00698 |
| Opus 5 | $0.00013 | $0.00349 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
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 8d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting: $ARGUMENTS.issue
You are helping troubleshoot "$ARGUMENTS.issue" in the repository: $ARGUMENTS.repo
Instructions
-
First, use
read_wiki_structurewithrepo_name: "$ARGUMENTS.repo"to find troubleshooting-related sections:- Troubleshooting guides
- FAQ
- Common issues / Known issues
- Migration guides (if the issue might be version-related)
-
Use
read_wiki_contentsto read relevant troubleshooting documentation -
Use
ask_questionwith targeted diagnostic questions:- "What causes $ARGUMENTS.issue and how do I fix it?"
- "What are common causes of $ARGUMENTS.issue?"
- "How do I debug $ARGUMENTS.issue?"
- "What configuration might cause $ARGUMENTS.issue?"
-
Present a structured troubleshooting guide:
Understanding the Issue
Brief explanation of what "$ARGUMENTS.issue" typically means in the context of $ARGUMENTS.repo.
Quick Fixes
Try these first - they solve the problem in most cases:
-
[Most Common Fix]
# Command or code to fixWhy this works: [brief explanation]
-
[Second Most Common Fix]
# Command or code -
[Third Option] ...
Diagnostic Steps
If quick fixes didn't work, follow these steps to identify the root cause:
-
Check X
# How to checkWhat to look for: ...
-
Verify Y ...
Common Causes & Solutions
Cause 1: [Description]
Symptoms: What you'd see if this is the cause Solution:
# How to fixCause 2: [Description]
Symptoms: ... Solution: ...
Cause 3: [Description]
...
Environment-Specific Issues
Issues that might be specific to:
- Windows: ...
- macOS: ...
- Linux: ...
- Docker: ...
Version Compatibility
Known issues with specific versions and how to resolve them.
Prevention
How to avoid this issue in the future.
-
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.
- 8d ago First seen · 106 lines · 25 tokens per session scan A f6627e650c80
troubleshoot is a command published in the GitHub repository qazi0/claude-plugins (8 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 698 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 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.
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.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.