orchestrate

orchestrate is a command for Claude Code from josix/agent-flow. It costs 0 tokens per session (6,467 once invoked), scanned B, original, MIT.

An orchestration command coordinates a complex task through multiple specialist agents working in sequence. It can track the task's phases and results in a project file.

In plain words
What is it for?
Use it to delegate a clearly described task, optionally reuse existing deep-dive context, and manage a staged agent workflow.
Why use it?
It gives multi-step work a defined process and records what has happened across the different stages.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the agent-flow plugin — 11 skills, 5 commands, 6 agents, 7 hooks shipped together

Good fit Use it to delegate a clearly described task, optionally reuse existing deep-dive context, and manage a staged agent workflow.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add josix/agent-flow
Claude Code
/plugin install agent-flow

Made for: Claude Code.

Or install agent-flow, the plugin that ships this one along with the rest of its 11 skills, 5 commands, 6 agents, 7 hooks.

Wrote 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.

agentmods badge for orchestrate

README.md
[![agentmods](https://agentmods.dev/badge/commands/josix/agent-flow/orchestrate/github.svg)](https://agentmods.dev/commands/josix/agent-flow/orchestrate)
Your own site
<a href="https://agentmods.dev/commands/josix/agent-flow/orchestrate"><img src="https://agentmods.dev/badge/commands/josix/agent-flow/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.

agentmods 80×15 button for orchestrate

Your own site · 80×15
<a href="https://agentmods.dev/commands/josix/agent-flow/orchestrate"><img src="https://agentmods.dev/badge/commands/josix/agent-flow/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,467 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.06467
Opus 5.5 $0.00000 $0.02587
Sonnet 5.5 $0.00000 $0.01293
Haiku 4.5 $0.00000 $0.00647

Measured 18d ago against content hash b17f0cb03dc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

orchestrate scanned grade B with 1 finding 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 18d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

TASK_COMPLEXITY=$(grep '^task_complexity:' .claude/orchestration.local.md | sed 's/task_complexity: *//' | tr -d '"' | tr '[:upper:]' '[:lower:]')
commands/orchestrate.md · 469 lines

How it starts

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

Orchestrate Command

Coordinate complex tasks through delegation to specialist agents.

Arguments

  • --use-deep-dive: Use existing deep-dive context to skip or accelerate exploration phase
  • <task description>: The task to orchestrate

How much of the pipeline runs is decided by the orchestrator, not by user flags — see Execution Profile.

State Initialization

FIRST: Initialize orchestration state by running:

# Check for --use-deep-dive flag
USE_DEEP_DIVE=false
TASK_ARGS="$ARGUMENTS"
if [[ "$ARGUMENTS" == *"--use-deep-dive"* ]]; then
  USE_DEEP_DIVE=true
  TASK_ARGS=$(echo "$ARGUMENTS" | sed 's/--use-deep-dive//' | xargs)
fi

bash ${CLAUDE_PLUGIN_ROOT}/scripts/init-orchestration.sh "$TASK_ARGS"

This creates .claude/orchestration.local.md to track:

  • Current phase and iteration
  • Gate results for each phase
  • Agent actions and timestamps

Prompt Refinement (Pre-Phase)

Ticket intake: if "$ARGUMENTS" contains an issue key (e.g. ABC-123) or a Jira/Atlassian/GitHub-issue URL and a matching tool is available (e.g. getJiraIssue, gh issue view), fetch the ticket first and seed the intent from it — Goal from the summary, Constraints and acceptance criteria from the description/ACs, and keep the key in the Goal so branch, commit, and PR names can carry it. Lawliet's intent-fidelity check then compares against the real acceptance criteria. Skip silently when no tool is available.

Apply the prompt-refinement skill to "$ARGUMENTS": if scope is genuinely ambiguous ask ONE clarifying question (with options); otherwise state a reasonable assumption and structure the task as Goal / Description / Actions / Constraints / Assumptions. Then:

  1. Classify task complexity using the task-classification skill tiers (Trivial / Exploratory / Implementation / Complex / Research). task_complexity is this tier, NOT complexipy code/cognitive complexity.

  2. Detect explicit written-report request: independently of the tier, set REPORT_REQUESTED_FLAG to true only if the user explicitly asked for a written report, investigation guide, or planning document.

Read the full file on GitHub · 469 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. 18d ago Changed · -207 lines b17f0cb03dc4
  2. 1mo ago First seen · 676 lines · 0 tokens per session scan B e2ede35d4fb3

Subscribe to this mod's changes

orchestrate is a command published in the GitHub repository josix/agent-flow (7 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,467 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.