A command for explaining code, software concepts, or how a system behaves in language suited to the reader's level.

Use it to explain a function, component, architecture, framework concept, or system behavior at a basic, intermediate, or advanced level.

It helps people understand unfamiliar or complex software by organizing the explanation progressively and adding examples, diagrams, or interactive elements when appropriate.

explain — Command by SuperClaude-Org

Install

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.

agentmods

npx agentmods add commands/superclaude-org/superclaude_framework/explain

Clone the repo

git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_Framework

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 700 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00700
Opus 5	$0.00009	$0.00350
Sonnet 5	$0.00003	$0.00140
Haiku 4.5	$0.00002	$0.00070

Measured 3d ago against content hash ad1db7933021, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

explain — 100% identical, 12 lines differ

plugins/superclaude/commands/explain.md · 92 lines

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: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: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

Read the full file on GitHub · 92 lines

Changes

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 ad1db7933021

Subscribe to this mod's changes

explain is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,856 stars, last pushed 12d ago), licensed MIT. It adds 17 tokens to every session and 700 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.

Learning and teaching workflow

learn

Learn Claude Code best practices and capture lessons into persistent memory.

rohitg00/pro-workflow · 0 tokens

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.

dwarvesf/dwarves-kit · 65 tokens

explain