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_plugin/sc-workflowgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWhat 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.00981 |
| Opus 5 | $0.00006 | $0.00491 |
| Sonnet 5 | $0.00002 | $0.00196 |
| Haiku 4.5 | $0.00001 | $0.00098 |
Grade A, and why
workflow 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.
This is a copy
88% identical to workflow — 35 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:sc:sc:workflow - Implementation Workflow Generator
Triggers
- PRD and feature specification analysis for implementation planning
- Structured workflow generation for development projects
- Multi-persona coordination for complex implementation strategies
- Cross-session workflow management and dependency mapping
Usage
/sc:sc:workflow [prd-file|feature-description] [--strategy systematic|agile|enterprise] [--depth shallow|normal|deep] [--parallel]
Behavioral Flow
- Analyze: Parse PRD and feature specifications to understand implementation requirements
- Plan: Generate comprehensive workflow structure with dependency mapping and task orchestration
- Coordinate: Activate multiple personas for domain expertise and implementation strategy
- Execute: Create structured step-by-step workflows with automated task coordination
- Validate: Apply quality gates and ensure workflow completeness across domains
Key behaviors:
- Multi-persona orchestration across architecture, frontend, backend, security, and devops domains
- Advanced MCP coordination with intelligent routing for specialized workflow analysis
- Systematic execution with progressive workflow enhancement and parallel processing
- Cross-session workflow management with comprehensive dependency tracking
MCP Integration
- Sequential MCP: Complex multi-step workflow analysis and systematic implementation planning
- Context7 MCP: Framework-specific workflow patterns and implementation best practices
- Magic MCP: UI/UX workflow generation and design system integration strategies
- Playwright MCP: Testing workflow integration and quality assurance automation
- Morphllm MCP: Large-scale workflow transformation and pattern-based optimization
- Serena MCP: Cross-session workflow persistence, memory management, and project context
Tool Coordination
- Read/Write/Edit: PRD analysis and workflow documentation generation
- TodoWrite: Progress tracking for complex multi-phase workflow execution
- Task: Advanced delegation for parallel workflow generation and multi-agent coordination
- WebSearch: Technology research, framework validation, and implementation strategy analysis
- sequentialthinking: Structured reasoning for complex workflow 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.
- 3d ago First seen · 118 lines · 12 tokens per session scan A 3f838f37a57c
workflow is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 13d ago), licensed MIT. It adds 12 tokens to every session and 981 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to workflow, differing in 35 lines, and is treated as a copy.
Other commands, from other repositories
brainstorm
Interactive requirements discovery through Socratic dialogue and systematic exploration.
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
checkpoint
Create a checkpoint by staging the changes you have made using git. usage: git [-v | --version] [-h | --help] [-C ] [-c = ] [--exec-path[= ]] [--html-path] [--man-path] [--info-path] [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare] [--git-dir= ] [--work-tree= ] [--namespace= ] [--super-prefix= ]…
greet
Generate contextual agent greeting using GreetingBuilder infrastructure.
image-node-prompt-pack
Build the dual-variant prompt pack, imagegen packet, and initial manifest using the selected library template.