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 commands/superclaude-org/superclaude_plugin/sc-explaingit 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-explain)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-explain"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-explain.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.00017 | $0.00714 |
| Opus 5 | $0.00009 | $0.00357 |
| Sonnet 5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
explain 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 3d 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.
This is a copy
100% identical to explain — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:sc:sc:explain - Code and Concept Explanation
Triggers
- Code understanding and documentation requests for complex functionality
- System behavior explanation needs for architectural components
- Educational content generation for knowledge transfer
- Framework-specific concept clarification requirements
Usage
/sc:sc:explain [target] [--level basic|intermediate|advanced] [--format text|examples|interactive] [--context domain]
Behavioral Flow
- Analyze: Examine target code, concept, or system for comprehensive understanding
- Assess: Determine audience level and appropriate explanation depth and format
- Structure: Plan explanation sequence with progressive complexity and logical flow
- Generate: Create clear explanations with examples, diagrams, and interactive elements
- Validate: Verify explanation accuracy and educational effectiveness
Key behaviors:
- Multi-persona coordination for domain expertise (educator, architect, security)
- Framework-specific explanations via Context7 integration
- Systematic analysis via Sequential MCP for complex concept breakdown
- Adaptive explanation depth based on audience and complexity
MCP Integration
- Sequential MCP: Auto-activated for complex multi-component analysis and structured reasoning
- Context7 MCP: Framework documentation and official pattern explanations
- Persona Coordination: Educator (learning), Architect (systems), Security (practices)
Tool Coordination
- Read/Grep/Glob: Code analysis and pattern identification for explanation content
- TodoWrite: Progress tracking for complex multi-part explanations
- Task: Delegation for comprehensive explanation workflows requiring systematic breakdown
Key Patterns
- Progressive Learning: Basic concepts → intermediate details → advanced implementation
- Framework Integration: Context7 documentation → accurate official patterns and practices
- Multi-Domain Analysis: Technical accuracy + educational clarity + security awareness
- Interactive Explanation: Static content → examples → interactive exploration
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.
- 3d ago First seen · 92 lines · 17 tokens per session scan A e13c5314d6f2
explain is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 13d ago), licensed MIT. It adds 17 tokens to every session and 714 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to explain, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
quiz-gate
The ★-tap NUDGE before merging a significant+worthy gate PR: a 5-question quiz built from the ACTUAL diff+tests, routed through deep-understand's mastery gate. Three logged responses (engage/defer/wave); advisory, never must-pass. Gates the human's attention, not the merge.
tutorial
Command "tutorial" from usurahi-project/usurahi, covering /tutorial, すること, 案内する要点 and 出力方針.
process-video
Convert lecture videos to transcripts and articles.
OPSX: Onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
/opsx-onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
OPSX: Onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.