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.
git clone --depth 1 https://github.com/shyftlabs/continuumWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/shyftlabs/continuum/orchestrator)<a href="https://agentmods.dev/commands/shyftlabs/continuum/orchestrator"><img src="https://agentmods.dev/badge/commands/shyftlabs/continuum/orchestrator.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00786 |
| Opus 5 | $0.00000 | $0.00393 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
orchestrator 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
100% identical to orchestrator — 0 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SPARC Orchestrator Mode
Purpose
Multi-agent task orchestration with TodoWrite/TodoRead/Task/Memory using MCP tools.
Activation
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "orchestrator",
task_description: "coordinate feature development"
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run orchestrator "coordinate feature development"
# For alpha features
npx claude-flow@alpha sparc run orchestrator "coordinate feature development"
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run orchestrator "coordinate feature development"
Core Capabilities
- Task decomposition
- Agent coordination
- Resource allocation
- Progress tracking
- Result synthesis
Integration Examples
Using MCP Tools (Preferred)
// Initialize orchestration swarm
mcp__claude-flow__swarm_init {
topology: "hierarchical",
strategy: "auto",
maxAgents: 8
}
// Spawn coordinator agent
mcp__claude-flow__agent_spawn {
type: "coordinator",
capabilities: ["task-planning", "resource-management"]
}
// Orchestrate tasks
mcp__claude-flow__task_orchestrate {
task: "feature development",
strategy: "parallel",
dependencies: ["auth", "ui", "api"]
}
Using NPX CLI (Fallback)
# Initialize orchestration swarm
npx claude-flow swarm init --topology hierarchical --strategy auto --max-agents 8
# Spawn coordinator agent
npx claude-flow agent spawn --type coordinator --capabilities "task-planning,resource-management"
# Orchestrate tasks
npx claude-flow task orchestrate --task "feature development" --strategy parallel --deps "auth,ui,api"
Orchestration Patterns
- Hierarchical coordination
- Parallel execution
- Sequential pipelines
- Event-driven flows
- Adaptive strategies
Coordination Tools
- TodoWrite for planning
- Task for agent launch
- Memory for sharing
- Progress monitoring
- Result aggregation
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 · 132 lines · 0 tokens per session scan A 29fab62338b6
orchestrator is a command published in the GitHub repository shyftlabs/continuum (84 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 786 tokens. A static security scan graded it A with 0 findings. It is 100% identical to orchestrator, differing in 0 lines, and is treated as a copy.
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.