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.
/plugin marketplace add josix/agent-flow/plugin install agent-flowWrote 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/josix/agent-flow/orchestrate)<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.
<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>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.06467 |
| Opus 5.5 | $0.00000 | $0.02587 |
| Sonnet 5.5 | $0.00000 | $0.01293 |
| Haiku 4.5 | $0.00000 | $0.00647 |
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:]') 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:
-
Classify task complexity using the
task-classificationskill tiers (Trivial / Exploratory / Implementation / Complex / Research).task_complexityis this tier, NOT complexipy code/cognitive complexity. -
Detect explicit written-report request: independently of the tier, set
REPORT_REQUESTED_FLAGtotrueonly if the user explicitly asked for a written report, investigation guide, or planning document.
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.
- 18d ago Changed · -207 lines b17f0cb03dc4
- 1mo ago First seen · 676 lines · 0 tokens per session scan B e2ede35d4fb3
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.
Other commands, from other repositories
security-scan
Run AgentShield against agent, hook, MCP, permission, and secret surfaces.
learn
Extract patterns and learnings from current session.
export-closedloop-learnings
Exports pending ClosedLoop learnings to global location with deduplication.
help
Quick reference for all Attune commands.
pm-roadmap
Generate or update the product roadmap. Spawns roadmap-planner. Outputs themed roadmap (Now / Next / Later) with rationale per theme.
t00-status
A status-report command for a T00 task workspace, using files that record communication, tasks, and the previous session's next steps.