What is orchestrator?

A command that switches the session into Orchestrator mode for managing multi-task development work. It uses project task data and helper agents to plan and carry out work.

Use it to resume project coordination, inspect the task dashboard, start work on an epic, or prepare prompts for helper agents.

It gives the agent a defined startup routine and a way to divide larger tasks between planning and implementation workers. It also checks the project’s current state before asking what to focus on.

How kryptobaseddev/cleo configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to kryptobaseddev/cleo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/kryptobaseddev/cleo/main/.claude/commands/orchestrator.md

Clone the repo

git clone --depth 1 https://github.com/kryptobaseddev/cleo

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/kryptobaseddev/cleo/orchestrator/github.svg)](https://agentmods.dev/commands/kryptobaseddev/cleo/orchestrator)

Your own site

<a href="https://agentmods.dev/commands/kryptobaseddev/cleo/orchestrator"><img src="https://agentmods.dev/badge/commands/kryptobaseddev/cleo/orchestrator/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/kryptobaseddev/cleo/orchestrator"><img src="https://agentmods.dev/badge/commands/kryptobaseddev/cleo/orchestrator.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 1,034 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01034
Opus 5.5	$0.00000	$0.00414
Sonnet 5.5	$0.00000	$0.00207
Haiku 4.5	$0.00000	$0.00103

Measured 1mo ago against content hash 3ce959d1b799, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

.claude/commands/orchestrator.md · 133 lines

How it starts

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

Orchestrator Mode (Claude Code)

Load the /ct-orchestrator skill. You are now the Orchestrator.

This command extends ct-orchestrator with Claude Code-specific operational guidance for spawning subagents via the Agent tool.

Session Startup

cleo session status              # Resume existing?
cleo dash                        # Project overview
cleo current                     # Active task?
cleo orchestrate start TXXX  # Full state + pipeline + next task

Then ask the human what they want to focus on today. Follow LOOM (RCASD -> IVTR) lifecycle for all work.

Agent Tool — Spawn Patterns

In Claude Code, subagent execution uses the Agent tool. The prompt comes from cleo orchestrate spawn.

Team Lead (RCASD planning, validation, complex reasoning)

Agent({
  description: "Team Lead: [epic domain] (T####)",
  subagent_type: "cleo-subagent",
  model: "sonnet",
  prompt: "<resolved prompt from cleo orchestrate spawn T####>"
})

Worker (focused implementation, testing)

Agent({
  description: "Worker: [task title] (T####)",
  subagent_type: "cleo-subagent",
  model: "sonnet",
  prompt: "<resolved prompt from cleo orchestrate spawn T####>"
})

Explorer (quick research, codebase investigation)

Agent({
  description: "Explorer: [research topic] (T####)",
  subagent_type: "cleo-subagent",
  model: "sonnet",
  prompt: "<resolved prompt from cleo orchestrate spawn T####>"
})

Parallel Spawn (independent tasks in same wave)

// Spawn multiple agents in a single message for parallel execution
Agent({
  description: "Worker: Task A (T1001)",
  subagent_type: "cleo-subagent",
  model: "sonnet",
  run_in_background: true,
  prompt: "<prompt A>"
})
Agent({
  description: "Worker: Task B (T1002)",
  subagent_type: "cleo-subagent",
  model: "sonnet",
  run_in_background: true,
  prompt: "<prompt B>"
})

Model Assignment

Role	Model	Rationale
Orchestrator (you)	opus	Strategic coordination, HITL interface
Team Leads	sonnet	Architecture, specs, validation
Workers	sonnet	Implementation, testing, focused changes
Explorers	sonnet	Quick research, codebase reads

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

1mo ago Changed 3ce959d1b799
1mo ago First seen · 133 lines · 0 tokens per session scan A 5f9bba8df8fe

Subscribe to this mod's changes

orchestrator is a command published in the GitHub repository kryptobaseddev/cleo (159 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,034 tokens. 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-30.

Planning Project management

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

fest-show

Show festival progression (in-progress tasks, roadmap, and dependency view).

Obedience-Corp/festival · 17 tokens

add-note

Add an internal or external note to a ConnectWise PSA ticket.

WYRE-AI/msp-claude-plugins · 12 tokens

dispatcher

Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…

Kanevry/session-orchestrator · 185 tokens

sync-linear

Sync current work with Linear ticket status.

bybren-llc/safe-agentic-workflow · 0 tokens

workpm

A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.

Dannykkh/skill-olympus · 31 tokens

cleo: Command for Claude Code