What is claude-orchestration?

A plugin for coordinating multiple coding agents on one complex feature. It delegates work, tracks tasks, and uses separate Git worktrees so agents can implement changes independently.

Use it to plan parallel agent tasks, coordinate their progress, and combine their implementations through a shared workflow.

It helps split large work into parallel pieces while keeping each agent's files and branch isolated.

claude-orchestration — Plugin for Claude Code by bengous

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.

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

Your own site

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

Per session not measured What this adds to a session before it is invoked.

When invoked not measured The manifest loads nothing itself; its 1 skill, 6 commands, 3 agents cost 174 tokens a session between them.

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.

Security

Grade A, and why

claude-orchestration 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 today.

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/.claude-plugin/plugin.json · 22 lines

What it actually says

{
  "name": "claude-orchestration",
  "version": "2.8.3",
  "description": "Parallel multi-agent orchestration for complex features with Task-based coordination and git-wt --stack worktree isolation",
  "author": {
    "name": "Augustin BENGOLEA",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/bengous/claude-code-plugins",
  "repository": "https://github.com/bengous/claude-code-plugins",
  "license": "MIT",
  "keywords": [
    "orchestration",
    "workflow",
    "automation",
    "multi-agent",
    "delegation",
    "git-worktree",
    "stack"
  ]
}

Contents

What it installs

The manifest is a name and a version. 1 skill, 6 commands, 3 agents travel with it, and installing the plugin installs all of them — 174 tokens a session between them. Each is measured on its own page, and each can be installed alone.

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.

today Changed bbbaf41212c4
26d ago Changed 1301d60c48d3
1mo ago Changed 38a5806bd6d1
1mo ago First seen · 22 lines scan A ff4251c74f78

Subscribe to this mod's changes

claude-orchestration is a plugin published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Building agents Claude Code Project management automation developer-tools workflow

taskwarrior

Token-dense recipes for taskwarrior CLI: dense listings, single-field lookups, batched exports, full-text search.

technicalpickles/pickled-claude-plugins · not measured

cc-code

A plugin that organizes software development into a fixed PM, architect, developer, and QA cycle, with separate files for requirements, design, implementation, and acceptance.

weiyi88/cc-code · not measured

pf-workflow

Spec-driven workflow toolkit for multi-agent CLI development: task packets, journal, retro, autopilot.

turvodnik/pf-workflow · not measured

weft

Deterministic workflow tracking with event-sourced logs for Claude Code.

dioptx/weft · not measured

ticket-flow

Beads-backed ticket workflow for Claude Code: spec → pickup → implement → finish behind verdict and merge gates, orchestrated by /flow (--local with resume, --parallel, --serial/--loop unattended queue runner), each ticket in its own git worktree. Five visible commands; the phase skills are model-invoked.

keefar/ticket-flow · not measured

csw

Ship a tracker ticket: dispatch it into a worktree, drive it to a pull request, merge it after review, and clean up after itself.

mikestankavich/claude-ship-workflow · not measured