task

A command for managing complex software tasks through structured workflows, delegation, and coordination between specialist roles.

In plain words
What is it for?
Use it for multi-part coding projects that need planning, parallel work, specialist input, tool routing, and quality checks.
Why use it?
It reduces the effort of breaking large projects into steps, assigning work, and checking whether the result is complete.

Command

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_plugin/sc-task
Clone the repo
git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_Plugin
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 988 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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00988
Opus 5 $0.00005 $0.00494
Sonnet 5 $0.00002 $0.00198
Haiku 4.5 $0.00001 $0.00099

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

Security

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.

commands/sc-task.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/sc:sc: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:sc:task [action] [target] [--strategy systematic|agile|enterprise] [--parallel] [--delegate]

Behavioral Flow

  1. Analyze: Parse task requirements and determine optimal execution strategy
  2. Delegate: Route to appropriate MCP servers and activate relevant personas
  3. Coordinate: Execute tasks with intelligent workflow management and parallel processing
  4. Validate: Apply quality gates and comprehensive task completion verification
  5. 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

Read the full file on GitHub · 116 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.

  1. 2d ago First seen · 116 lines · 11 tokens per session scan A a2904c502dca

Subscribe to this mod's changes

task is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 12d ago), licensed MIT. It adds 11 tokens to every session and 988 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.