What is cc-orchestrate?

A conductor command that routes one backlog item through definition, implementation planning, coding, and verification. It coordinates separate agents and records the run's handoffs and limits.

Use it to take one planned piece of work from a backlog through specification, plan creation, implementation, review, and test verification.

It keeps a multi-step coding task ordered and constrained, so agents work from approved documents and do not write outside their assigned areas.

How yeisonrestrepo/code-conductor configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to yeisonrestrepo/code-conductor. 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/yeisonrestrepo/code-conductor/main/.claude/commands/cc-orchestrate.md

Clone the repo

git clone --depth 1 https://github.com/yeisonrestrepo/code-conductor

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/yeisonrestrepo/code-conductor/cc-orchestrate/github.svg)](https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-orchestrate)

Your own site

<a href="https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-orchestrate"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-orchestrate"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,666 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.00019	$0.03666
Opus 5.5	$0.00008	$0.01466
Sonnet 5.5	$0.00004	$0.00733
Haiku 4.5	$0.00002	$0.00367

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

Security

Grade A, and why

cc-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 23d 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/cc-orchestrate.md · 156 lines

How it starts

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

/cc-orchestrate [--auto] [--ticket <N|issue URL>]

You are the orchestrator for one run (FEAT-011). You hold no repository write access. You never write a tracked file, and while the run is live Guard 6 denies any write-family call outside your write surface:

.claude/memory/orchestrator-run.json
.claude/memory/band-envelope.json
.claude/memory/session-snapshot.json
.conductor/**

You move work only through orchestrate.mjs and the Agent tool. Release, project.md and the closeout stay with the human. Bash is outside Guard 6, as it is outside Guard 5: never use it to write a repository file.

Resolve the script (D11)

Begin every Bash call that runs the script with the same resolution, the deployed copy first, then source:

S=.claude/scripts; [ -f "$S/orchestrate.mjs" ] || S=scripts

Then run node "$S/orchestrate.mjs" <verb> ... in that same call. The exit codes:

0: success.
1: a halt. The code and the reason are on stderr and recorded in the run file.
2: a refusal. Nothing was written. Read the message: it names the step the run is actually at.

On any halt

Print the stderr line verbatim.
Dispatch nothing further. If an agent is still in flight, wait for its completion notice before you report the halt; its writes stay bounded by the envelope in force. Then stop.

A halt is terminal in v1 (D12). Recovery is node "$S/orchestrate.mjs" end, then a fresh start, each only on the owner's word.

Steps

Start. Run node "$S/orchestrate.mjs" start $ARGUMENTS. It resolves the run's test command before it writes anything, and its stdout ends with test command: <command>.
- If stdout names a replaced stale run, report its item and start time.
- On ORCH_RUN_ACTIVE, report it, offer end, and stop.
- On ORCH_TEST_COMMAND_UNRESOLVED or ORCH_TEST_COMMAND_UNSAFE, report it and stop. No run file was written, so there is nothing to end. The owner adds a test script to package.json, or removes the chaining from the command it names, before a fresh start.
- On an intake halt (TICKET_FLAG_INVALID, TICKET_UNREACHABLE, TICKET_NOT_ISSUE, TICKET_CLOSED, TICKET_BODY_EMPTY or TICKET_BODY_OVER_CAP), report it and stop. No run file and no snapshot were written; the halt names its remedy.
- With --ticket, stdout also names the ticket, its title, the snapshot .conductor/ticket/<ITEM>.md and its sha256. The run is bound.

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

23d ago Changed · +61 lines 1f6ef4b240b6
27d ago First seen · 95 lines · 19 tokens per session scan A ffd0e64698b8

Subscribe to this mod's changes

cc-orchestrate is a command published in the GitHub repository yeisonrestrepo/code-conductor (17 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 3,666 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-10-03.

Building agents Project management agentic-development ai-agents claude claudecode skills spec-driven-development

code-conductor: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/cc-orchestrate [--auto] [--ticket <N|issue URL>]

Resolve the script (D11)

On any halt

Steps

What this file has done since we first saw it

Other commands, from other repositories

update-deps

flow-start

add-to-todos

create-issue

triage-issues

create-ticket