Borrowing it
Nothing to install: this file belongs to Everyone-Needs-A-Copilot/claude-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Everyone-Needs-A-Copilot/claude-copilot/main/.claude/commands/orchestrate.mdgit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/everyone-needs-a-copilot/claude-copilot/orchestrate)<a href="https://agentmods.dev/commands/everyone-needs-a-copilot/claude-copilot/orchestrate"><img src="https://agentmods.dev/badge/commands/everyone-needs-a-copilot/claude-copilot/orchestrate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/everyone-needs-a-copilot/claude-copilot/orchestrate"><img src="https://agentmods.dev/badge/commands/everyone-needs-a-copilot/claude-copilot/orchestrate.svg" alt="Reviewed on agentmods" width="80" 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.00015 | $0.01305 |
| Opus 5.5 | $0.00006 | $0.00522 |
| Sonnet 5.5 | $0.00003 | $0.00261 |
| Haiku 4.5 | $0.00002 | $0.00130 |
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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate Command
Scaffolding layer for parallel streams. Agent dispatch is handled by the harness, not by this command.
/orchestrate generate # Create PRD + stream tasks via @agent-ta
/orchestrate start # Validate streams, check conflicts, create worktrees, print dispatch cmds
/orchestrate status # Show stream progress + live sessions
/orchestrate merge # Merge completed worktrees back to main branch
generate (default if no subcommand)
Creates PRD and tasks with stream metadata. Prompt user for feature description if not provided.
- Invoke @agent-ta to design architecture and return structured JSON:
{
"prd": { "title": "...", "description": "...", "content": "# PRD..." },
"tasks": [{
"title": "...", "description": "...",
"metadata": {
"streamId": "Stream-A", "streamName": "Foundation",
"files": ["src/auth.ts"], "dependencies": []
}
}]
}
- Parse JSON, validate (no cycles, at least one task with
dependencies: []) - Persist real rows for
start:tc prd create --title "..." --description "..." --json(capture<prd-id>); per uniquestreamId,tc stream create --name "<streamName>" --prd <prd-id> --json(capture the numericid); then per task,tc task create --title "..." --prd <prd-id> --stream <numeric-id> --description "..." --metadata '<json>' --json. Skipping--stream/--metadataleavestc stream conflictsandtc task list --stream <id>empty. - Display plan summary and ask user to approve
start
Validates streams, checks for real file conflicts, creates an isolated git
worktree per ready stream, and prints exact dispatch commands (claude --bg
or tc worker).
tc stream list --json-- stop if no streams (tell user to rungeneratefirst)- Preflight: confirm
tcis on PATH, you're inside a git repo, and the working tree is clean tc stream conflicts --json(hard precondition) -- non-zero exit means a file is claimed by multiple streams. Report the conflicts; stop before creating worktrees.- For each stream whose dependencies are all satisfied, create an isolated worktree:
git worktree add .worktrees/<stream-id> -b stream/<stream-id> - Print one dispatch command per ready stream; each agent works in
.worktrees/<stream-id>on that stream's tasks (tc task list --stream <stream-id> --json):
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.
- 1mo ago First seen · 132 lines · 15 tokens per session scan A d088e64cb3ec
orchestrate is a command published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (14 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 1,305 once invoked, about $0.0001 per session on Opus 5.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-09-04.
Other commands, from other repositories
epic-sync
Sync epic issue bodies, labels, and local coordination snapshots from GitHub.
portfolio-status
Review the health of all projects in the portfolio.
release
You are a meticulous release manager. You coordinate releases, maintain changelogs, manage versioning, and ensure every release ships with proper documentation and rollback plans. You have zero tolerance for "just push it to prod" releases.
create-issue
Open a GitHub issue on the Ion repo for a bug or feature request derived from the current conversation, with consumer project details scrubbed.
mission
Use when work must be provably done, not just finished: governed missions with a durable .ai/ ledger, worker attestation, evidence-gated status, provenance, collision-aware wave planning, agent registry, and process ownership. Triggers: parallel or multi-agent execution, 'is this actually integrated?', 'prove the…
weekly-review
Produce a weekly review from the evidence in the repository and the workspace: commits and pull requests merged or open, issues closed and opened, decisions logged, research log entries, action items done and overdue, and what stalled, then a short plan for next week; written to a dated file so reviews accumulate. Use…