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/scgit 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.00019 | $0.00677 |
| Opus 5 | $0.00010 | $0.00338 |
| Sonnet 5 | $0.00004 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
sc 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SuperClaude Command Dispatcher
🚀 SuperClaude Framework - Main command dispatcher
Usage
All SuperClaude commands use the /sc: prefix:
/sc:command [args...]
Available Commands
Research & Analysis
/sc:research [query] - Deep web research with parallel search
Repository Management
/sc:index-repo - Index repository for context optimization
AI Agents
/sc:agent [type] - Launch specialized AI agents
Recommendations
/sc:recommend [context] - Get command recommendations
Help
/sc - Show this help (all available commands)
Command Namespace
All commands are namespaced under sc: to keep them organized:
- ✅
/sc:research query - ✅
/sc:index-repo - ✅
/sc:agent type - ✅
/sc:recommend - ✅
/sc(help)
Examples
Research
/sc:research React 18 new features
/sc:research LLM agent architectures 2024
/sc:research Python async best practices
Index Repository
/sc:index-repo
Agent
/sc:agent deep-research
/sc:agent self-review
/sc:agent repo-index
Recommendations
/sc:recommend
Quick Reference
| Command | Description | Example |
|---|---|---|
/sc:research |
Deep web research | /sc:research topic |
/sc:index-repo |
Repository indexing | /sc:index-repo |
/sc:agent |
Specialized AI agents | /sc:agent type |
/sc:recommend |
Command suggestions | /sc:recommend |
/sc |
Show help | /sc |
Features
- Parallel Execution: Research runs multiple searches in parallel
- Evidence-Based: All findings backed by sources
- Context-Aware: Uses repository context when available
- Token Efficient: Optimized for minimal token usage
Help
For help on specific commands:
/sc:research --help
/sc:agent --help
Or use the main help command:
/sc
Check the documentation:
- PLANNING.md - Architecture and design
- TASK.md - Current tasks and priorities
- KNOWLEDGE.md - Tips and best practices
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 · 131 lines · 19 tokens per session scan A 7cdebbca0006
sc is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,856 stars, last pushed 12d ago), licensed MIT. It adds 19 tokens to every session and 677 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.