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/spawngit 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.00012 | $0.00702 |
| Opus 5 | $0.00006 | $0.00351 |
| Sonnet 5 | $0.00002 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
spawn 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- spawn — 92% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:spawn - Meta-System Task Orchestration
Triggers
- Complex multi-domain operations requiring intelligent task breakdown
- Large-scale system operations spanning multiple technical areas
- Operations requiring parallel coordination and dependency management
- Meta-level orchestration beyond standard command capabilities
Usage
/sc:spawn [complex-task] [--strategy sequential|parallel|adaptive] [--depth normal|deep]
Behavioral Flow
- Analyze: Parse complex operation requirements and assess scope across domains
- Decompose: Break down operation into coordinated subtask hierarchies
- Orchestrate: Execute tasks using optimal coordination strategy (parallel/sequential)
- Monitor: Track progress across task hierarchies with dependency management
- Integrate: Aggregate results and provide comprehensive orchestration summary
Key behaviors:
- Meta-system task decomposition with Epic → Story → Task → Subtask breakdown
- Intelligent coordination strategy selection based on operation characteristics
- Cross-domain operation management with parallel and sequential execution patterns
- Advanced dependency analysis and resource optimization across task hierarchies
MCP Integration
- Native Orchestration: Meta-system command uses native coordination without MCP dependencies
- Progressive Integration: Coordination with systematic execution for progressive enhancement
- Framework Integration: Advanced integration with SuperClaude orchestration layers
Tool Coordination
- TodoWrite: Hierarchical task breakdown and progress tracking across Epic → Story → Task levels
- Read/Grep/Glob: System analysis and dependency mapping for complex operations
- Edit/MultiEdit/Write: Coordinated file operations with parallel and sequential execution
- Bash: System-level operations coordination with intelligent resource management
Key Patterns
- Hierarchical Breakdown: Epic-level operations → Story coordination → Task execution → Subtask granularity
- Strategy Selection: Sequential (dependency-ordered) → Parallel (independent) → Adaptive (dynamic)
- Meta-System Coordination: Cross-domain operations → resource optimization → result integration
- Progressive Enhancement: Systematic execution → quality gates → comprehensive validation
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.
- 2d ago First seen · 85 lines · 12 tokens per session scan A fa49398ce13d
spawn is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,856 stars, last pushed 12d ago), licensed MIT. It adds 12 tokens to every session and 702 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
estimate
Provide development estimates for tasks, features, or projects with intelligent analysis.
task
Execute complex tasks with intelligent workflow management and delegation.
spawn
Meta-system task orchestration with intelligent breakdown and delegation.
index
Generate comprehensive project documentation and knowledge base with intelligent organization.
reflect
Task reflection and validation using Serena MCP analysis capabilities.
select-tool
Intelligent MCP tool selection based on complexity scoring and operation analysis.