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/taskgit 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.00773 |
| Opus 5 | $0.00005 | $0.00387 |
| Sonnet 5 | $0.00002 | $0.00155 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
task 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:task - Enhanced Task Management
Triggers
- Complex tasks requiring multi-agent coordination and delegation
- Projects needing structured workflow management and cross-session persistence
- Operations requiring intelligent MCP server routing and domain expertise
- Tasks benefiting from systematic execution and progressive enhancement
Usage
/sc:task [action] [target] [--strategy systematic|agile|enterprise] [--parallel] [--delegate]
Behavioral Flow
- Analyze: Parse task requirements and determine optimal execution strategy
- Delegate: Route to appropriate MCP servers and activate relevant personas
- Coordinate: Execute tasks with intelligent workflow management and parallel processing
- Validate: Apply quality gates and comprehensive task completion verification
- Optimize: Analyze performance and provide enhancement recommendations
Key behaviors:
- Multi-persona coordination across architect, frontend, backend, security, devops domains
- Intelligent MCP server routing (Sequential, Context7, Magic, Playwright, Morphllm, Serena)
- Systematic execution with progressive task enhancement and cross-session persistence
- Advanced task delegation with hierarchical breakdown and dependency management
MCP Integration
- Sequential MCP: Complex multi-step task analysis and systematic execution planning
- Context7 MCP: Framework-specific patterns and implementation best practices
- Magic MCP: UI/UX task coordination and design system integration
- Playwright MCP: Testing workflow integration and validation automation
- Morphllm MCP: Large-scale task transformation and pattern-based optimization
- Serena MCP: Cross-session task persistence and project memory management
Tool Coordination
- TodoWrite: Hierarchical task breakdown and progress tracking across Epic → Story → Task levels
- Task: Advanced delegation for complex multi-agent coordination and sub-task management
- Read/Write/Edit: Task documentation and implementation coordination
- sequentialthinking: Structured reasoning for complex task dependency analysis
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 · 89 lines · 11 tokens per session scan A faf49cbb87d9
task 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 773 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
template
Manage issue templates for streamlined issue creation.
project-recap
Generate a visual project recap for context switching.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.
sync-linear
Sync current work with Linear ticket status.