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/SuperClaude-Org/SuperClaude_PluginWrote 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/superclaude-org/superclaude_plugin/sc-troubleshoot)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-troubleshoot"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-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.00019 | $0.00877 |
| Opus 5 | $0.00010 | $0.00439 |
| Sonnet 5 | $0.00004 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00088 |
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:sc:sc:troubleshoot - Issue Diagnosis and Resolution
Triggers
- Code defects and runtime error investigation requests
- Build failure analysis and resolution needs
- Performance issue diagnosis and optimization requirements
- Deployment problem analysis and system behavior debugging
Usage
/sc:sc:troubleshoot [issue] [--type bug|build|performance|deployment] [--trace] [--fix]
Behavioral Flow
- Analyze: Examine issue description and gather relevant system state information
- Investigate: Identify potential root causes through systematic pattern analysis
- Debug: Execute structured debugging procedures including log and state examination
- Propose: Validate solution approaches with impact assessment and risk evaluation
- Resolve: Apply appropriate fixes and verify resolution effectiveness
Key behaviors:
- Systematic root cause analysis with hypothesis testing and evidence collection
- Multi-domain troubleshooting (code, build, performance, deployment)
- Structured debugging methodologies with comprehensive problem analysis
- Safe fix application with verification and documentation
Tool Coordination
- Read: Log analysis and system state examination
- Bash: Diagnostic command execution and system investigation
- Grep: Error pattern detection and log analysis
- Write: Diagnostic reports and resolution documentation
Key Patterns
- Bug Investigation: Error analysis → stack trace examination → code inspection → fix validation
- Build Troubleshooting: Build log analysis → dependency checking → configuration validation
- Performance Diagnosis: Metrics analysis → bottleneck identification → optimization recommendations
- Deployment Issues: Environment analysis → configuration verification → service validation
Examples
Code Bug Investigation
/sc:sc:troubleshoot "Null pointer exception in user service" --type bug --trace
# Systematic analysis of error context and stack traces
# Identifies root cause and provides targeted fix recommendations
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 · 120 lines · 19 tokens per session scan A 1b12a7616b82
troubleshoot is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 18d ago), licensed MIT. It adds 19 tokens to every session and 877 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-30.
Other commands, from other repositories
analyze
Comprehensive code analysis across quality, security, performance, and architecture domains.
troubleshoot
Diagnose and resolve issues in code, builds, deployments, and system behavior.
codegraph
Generate or refresh a codebase knowledge graph (graphify) at its fixed graphify-out/ location so other skills can query cross-file relationships. Piloting — re-run after code changes.
analyze
Comprehensive code analysis across quality, security, performance, and architecture domains.
troubleshoot
Diagnose and resolve issues in code, builds, deployments, and system behavior.
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…