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_framework/helpgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWhat 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.00011 | $0.01722 |
| Opus 5 | $0.00005 | $0.00861 |
| Sonnet 5 | $0.00002 | $0.00344 |
| Haiku 4.5 | $0.00001 | $0.00172 |
Grade B, and why
help scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Execute any commands or create any files Copies of this mod
1 near-identical copy found in the catalogue:
- help — 92% identical, 66 lines differ
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:help - Command Reference Documentation
Triggers
- Command discovery and reference lookup requests
- Framework exploration and capability understanding needs
- Documentation requests for available SuperClaude commands
Behavioral Flow
- Display: Present complete command list with descriptions
- Complete: End interaction after displaying information
Key behaviors:
- Information display only - no execution or implementation
- Reference documentation mode without action triggers
Here is a complete list of all available SuperClaude (/sc) commands.
| Command | Description |
|---|---|
/sc:analyze |
Comprehensive code analysis across quality, security, performance, and architecture domains |
/sc:brainstorm |
Interactive requirements discovery through Socratic dialogue and systematic exploration |
/sc:build |
Build, compile, and package projects with intelligent error handling and optimization |
/sc:business-panel |
Multi-expert business analysis with adaptive interaction modes |
/sc:cleanup |
Systematically clean up code, remove dead code, and optimize project structure |
/sc:design |
Design system architecture, APIs, and component interfaces with comprehensive specifications |
/sc:document |
Generate focused documentation for components, functions, APIs, and features |
/sc:estimate |
Provide development estimates for tasks, features, or projects with intelligent analysis |
/sc:explain |
Provide clear explanations of code, concepts, and system behavior with educational clarity |
/sc:git |
Git operations with intelligent commit messages and workflow optimization |
/sc:help |
List all available /sc commands and their functionality |
/sc:implement |
Feature and code implementation with intelligent persona activation and MCP integration |
/sc:improve |
Apply systematic improvements to code quality, performance, and maintainability |
/sc:index |
Generate comprehensive project documentation and knowledge base with intelligent organization |
/sc:load |
Session lifecycle management with Serena MCP integration for project context loading |
/sc:reflect |
Task reflection and validation using Serena MCP analysis capabilities |
/sc:save |
Session lifecycle management with Serena MCP integration for session context persistence |
/sc:select-tool |
Intelligent MCP tool selection based on complexity scoring and operation analysis |
/sc:spawn |
Meta-system task orchestration with intelligent breakdown and delegation |
/sc:spec-panel |
Multi-expert specification review and improvement using renowned specification and software engineering experts |
/sc:task |
Execute complex tasks with intelligent workflow management and delegation |
/sc:test |
Execute tests with coverage analysis and automated quality reporting |
/sc:troubleshoot |
Diagnose and resolve issues in code, builds, deployments, and system behavior |
/sc:workflow |
Generate structured implementation workflows from PRDs and feature requirements |
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 · 149 lines · 11 tokens per session scan B d1b803820430
help is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,856 stars, last pushed 12d ago), licensed MIT. It adds 11 tokens to every session and 1,722 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
dashboard
Running banco with no subcommand opens a full-screen, read-only dashboard for the current project.
tidy
Reports module data that the current configuration no longer backs — repositories dropped from a provider, task trees whose syncing was turned off, and local items you may want to retire. The output is JSON, intended for agents (see the tidy skill).
check
Scans the project directory for content that does not belong to any module and reports it.
troubleshoot
Diagnose and resolve issues in code, builds, deployments, and system behavior.
sync
Pulls data from configured remote providers and writes it to the local filesystem.
analyze
Comprehensive code analysis across quality, security, performance, and architecture domains.