A command that breaks a development task into smaller jobs and delegates them to background coding agents. It can monitor their progress, combine their results, and continue or stop a session.

Running independent subtasks in parallel, watching agent progress, reviewing an execution timeline, compressing a long chat, resuming work, or aborting active agents.

It reduces the need to coordinate several agents and track each partial result yourself. Different modes adapt the work to quick tasks, debugging, optimization, or release checks.

orchestrate — Command by Data-Wise

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/data-wise/claude-plugins/orchestrate

Clone the repo

git clone --depth 1 https://github.com/Data-Wise/claude-plugins

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,029 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.

Model	Per session	Once invoked
Fable 5	$0.00022	$0.02029
Opus 5	$0.00011	$0.01014
Sonnet 5	$0.00004	$0.00406
Haiku 4.5	$0.00002	$0.00203

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

Security

Grade A, and why

orchestrate 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 yesterday.

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.

craft/commands/orchestrate.md · 286 lines

How it starts

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

/craft:orchestrate — Launch Orchestrator Mode

Usage

/craft:orchestrate <task>              # Start with default mode
/craft:orchestrate <task> <mode>       # Start with specific mode
/craft:orchestrate status              # Show agent dashboard
/craft:orchestrate timeline            # Show execution timeline
/craft:orchestrate compress            # Force chat compression
/craft:orchestrate continue            # Resume previous session
/craft:orchestrate abort               # Stop all agents

Modes (NEW in v1.1.0)

Mode	Max Agents	Compression	Use Case
`default`	2	70%	Quick tasks
`debug`	1 (sequential)	90%	Troubleshooting
`optimize`	4	60%	Fast parallel work
`release`	4	85%	Pre-release audit

/craft:orchestrate "add auth" optimize    # Fast parallel
/craft:orchestrate "prep release" release # Thorough audit
/craft:orchestrate "debug login" debug    # Sequential verbose

What It Does

Activates Orchestrator v2.1 mode which:

Analyzes your task and decomposes into subtasks
Spawns background subagents to work in parallel
Monitors progress with visual status dashboard
Tracks context usage with token estimation
Compresses chat when approaching limits
Reports results with ADHD-friendly formatting

Examples

Start Orchestrated Workflow

/craft:orchestrate "add user authentication with OAuth"

## 📋 TASK ANALYSIS

**Request**: Add OAuth authentication
**Complexity**: complex
**Mode**: default (2 agents max)
**Estimated subtasks**: 5
**Delegation strategy**: hybrid

| # | Task | Agent | Priority | Dependencies |
|---|------|-------|----------|--------------|
| 1 | Design auth flow | arch | P0 | none |
| 2 | Implement backend | code | P0 | 1 |
| 3 | Create login UI | code | P1 | 1 |
| 4 | Add tests | test | P1 | 2,3 |
| 5 | Update docs | doc | P2 | 2 |

Spawning agents...

Fast Parallel Mode

/craft:orchestrate "add tests for all endpoints" optimize

## 🚀 ORCHESTRATOR v2.1 — OPTIMIZE MODE

**Configuration**:
- Max parallel agents: 4
- Compression threshold: 60%
- Output verbosity: Minimal
- Strategy: Aggressive parallelization

Spawning 4 test agents in parallel...

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

yesterday First seen · 286 lines · 22 tokens per session scan A ec461dfed03d

Subscribe to this mod's changes

orchestrate is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 6d ago), licensed MIT. It adds 22 tokens to every session and 2,029 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-31.

Building agents Planning smart

verify

Adversarial spec-vs-implementation verification for a completed task. Dispatches the spec-mentor subagent with fresh context (no anchoring bias), parses its verdict (PASS / DRIFT / NEEDS-MARTY), and updates the verification queue. The v7.4.0 architectural replacement for a dedicated "mentor session.".

MartyBonacci/specswarm · 68 tokens

orchestrate