A command for coordinating complex feature work across multiple coding agents. It gathers codebase context, gets architectural agreement, creates isolated worktrees, runs implementation work, and reviews the results.

Use it to plan, execute, merge, review, and prepare parallel agent changes for shipping.

It provides an organized process for splitting complex work while managing dependencies, integration, and final review.

orc — Command for Claude Code by bengous/claude-code-plugins

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/bengous/claude-code-plugins

Made for: Claude Code.

Or install claude-orchestration, the plugin that ships this one along with the rest of its 1 skill, 6 commands, 3 agents.

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/bengous/claude-code-plugins/orc/github.svg)](https://agentmods.dev/commands/bengous/claude-code-plugins/orc)

Your own site

<a href="https://agentmods.dev/commands/bengous/claude-code-plugins/orc"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/orc/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/bengous/claude-code-plugins/orc"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/orc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,707 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.00008	$0.02707
Opus 5.5	$0.00003	$0.01083
Sonnet 5.5	$0.00002	$0.00541
Haiku 4.5	$0.00001	$0.00271

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

Security

Grade A, and why

orc 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 26d 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.

orchestration/commands/orc.md · 382 lines

How it starts

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

Parallel orchestration workflow

Dependency: Requires git-worktree plugin installed (/plugin install git-worktree@bengous-plugins then /git-worktree:worktree-setup).

<phase_1 title="Understand & Plan">

Goal: Gather context, get architect consensus, and get approval

Initial request: $ARGUMENTS

Step 1: Track the Phases

Track the three phases as tasks (TaskCreate, TaskUpdate) so the user can follow progress.

Step 2: Inline Exploration

Explore the codebase directly until you can summarize the relevant code, the patterns and conventions to follow, the integration points, and the files to change.

Step 3: Clarify If Needed

Ask about scope, design preferences, or edge cases only if truly ambiguous. Proceed autonomously when requirements are reasonably clear.

Step 4: Define Chunks

Break into 2-4 independent chunks with minimal file overlap:

Chunk 1: [Name] - [Description]
  Files: [list]
Chunk 2: [Name] - [Description]
  Files: [list]

Step 5: Architect Consensus

Spawn 2-3 architect agents in parallel using the subagent dispatch pattern:

Before: Pre-truncate output files

Write(file_path: ".claude/orc-state/architect-minimal.md", content: "")
Write(file_path: ".claude/orc-state/architect-clean.md", content: "")
Write(file_path: ".claude/orc-state/architect-pragmatic.md", content: "")

Dispatch: Spawn all architects in parallel (single message)

Issue all three Agent calls in ONE message — that is what makes them run concurrently.

Agent(
  description: "Architect: Minimal changes",
  subagent_type: "claude-orchestration:architect",
  prompt: """
    You are the MINIMAL architect. Focus: smallest diff, maximum code reuse, least disruption.

    Context: [Feature description, codebase findings, chunk breakdown, constraints]

    Write your architecture proposal to .claude/orc-state/architect-minimal.md

    Include: approach overview, file changes per chunk, key decisions with rationale
  """
)

Agent(
  description: "Architect: Clean architecture",
  subagent_type: "claude-orchestration:architect",
  prompt: """
    You are the CLEAN architect. Focus: maintainability, clear abstractions, long-term health.

    Context: [Feature description, codebase findings, chunk breakdown, constraints]

    Write your architecture proposal to .claude/orc-state/architect-clean.md

    Include: approach overview, file changes per chunk, key decisions with rationale
  """
)

Agent(
  description: "Architect: Pragmatic balance",
  subagent_type: "claude-orchestration:architect",
  prompt: """
    You are the PRAGMATIC architect. Focus: practical trade-offs, ship-ready approach.

    Context: [Feature description, codebase findings, chunk breakdown, constraints]

    Write your architecture proposal to .claude/orc-state/architect-pragmatic.md

    Include: approach overview, file changes per chunk, key decisions with rationale
  """
)

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

26d ago Changed · -69 lines fafe8620ac26
1mo ago First seen · 451 lines · 8 tokens per session scan A 218e649998e3

Subscribe to this mod's changes

orc is a command published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 2,707 once invoked, about $0.0000 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-03.

Claude Code Commits Git and workflow Project management automation developer-tools workflow

orc

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Parallel orchestration workflow

Step 1: Track the Phases

Step 2: Inline Exploration

Step 3: Clarify If Needed

Step 4: Define Chunks

Step 5: Architect Consensus

Before: Pre-truncate output files

Dispatch: Spawn all architects in parallel (single message)

What this file has done since we first saw it

Other commands, from other repositories

make-pr

land

standup

gsd:remove-phase

company-repo

iterate