orchestrate

orchestrate is a command for coding agents from xu-xiang/everything-claude-code-zh. It costs 17 tokens per session (799 once invoked), scanned A, original, MIT.

A command for coordinating several specialised agents on a complex task.

In plain words
What is it for?
Use it to plan and coordinate agents for design, implementation, testing, code review, security review, documentation, database work, or build fixes.
Why use it?
It helps split work into dependent or independent parts and combine the results into one outcome.

Command

Part of the everything-claude-code-zh plugin — 17 skills, 26 commands, 13 agents shipped together

About the project

everything-claude-code-zh is a Chinese translation of a collection of configurations for Claude Code and other AI coding agents. It provides agents, skills, hooks, commands, rules, and MCP configurations intended to support development workflows such as memory persistence, security scanning, evaluation, and research-first work. The catalogue includes commands, skills, agents, instructions, and a plugin from this configuration set.

xu-xiang/everything-claude-code-zh · 1,929 stars · on GitHub

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.

agentmods
npx agentmods add commands/xu-xiang/everything-claude-code-zh/orchestrate
Clone the repo
git clone --depth 1 https://github.com/xu-xiang/everything-claude-code-zh

Or install everything-claude-code-zh, the plugin that ships this one along with the rest of its 17 skills, 26 commands, 13 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.

agentmods badge for orchestrate

README.md
[![agentmods](https://agentmods.dev/badge/commands/xu-xiang/everything-claude-code-zh/orchestrate.svg)](https://agentmods.dev/commands/xu-xiang/everything-claude-code-zh/orchestrate)
Your own site
<a href="https://agentmods.dev/commands/xu-xiang/everything-claude-code-zh/orchestrate"><img src="https://agentmods.dev/badge/commands/xu-xiang/everything-claude-code-zh/orchestrate.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 799 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00799
Opus 5 $0.00009 $0.00400
Sonnet 5 $0.00003 $0.00160
Haiku 4.5 $0.00002 $0.00080

Measured 5d ago against content hash 68493e1e8fda, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.opencode/commands/orchestrate.md · 89 lines

What it actually says

编排(Orchestrate)命令

为此复杂任务编排多个专业智能体(Agent):$ARGUMENTS

你的任务

  1. 分析任务复杂度并分解为子任务
  2. 为每个子任务确定最佳智能体(Agent)
  3. 创建执行计划并明确依赖关系
  4. 协调执行 - 尽可能并行处理
  5. 将结果**汇总(Synthesize)**为统一输出

可用的智能体(Available Agents)

智能体(Agent) 专长 适用场景
planner 实施规划 复杂功能设计
architect 系统设计 架构决策
code-reviewer 代码质量 审查变更
security-reviewer 安全分析 漏洞检测
tdd-guide 测试驱动开发 功能实现
build-error-resolver 构建修复 TypeScript/构建错误
e2e-runner E2E 测试 用户流程测试
doc-updater 文档编写 更新文档
refactor-cleaner 代码清理 冗余代码移除
go-reviewer Go 代码 Go 特有的代码审查
go-build-resolver Go 构建 Go 构建错误
database-reviewer 数据库 查询优化

编排模式(Orchestration Patterns)

顺序执行(Sequential Execution)

planner → tdd-guide → code-reviewer → security-reviewer

适用场景:后续任务依赖于前期结果。

并行执行(Parallel Execution)

┌→ security-reviewer
planner →├→ code-reviewer
└→ architect

适用场景:任务之间相互独立。

扇出/扇入(Fan-Out/Fan-In)

         ┌→ agent-1 ─┐
planner →├→ agent-2 ─┼→ synthesizer
         └→ agent-3 ─┘

适用场景:需要多个维度的视角。

执行计划格式

阶段 1:[名称]

  • 智能体(Agent):[agent-name]
  • 任务:[具体任务内容]
  • 依赖项:[无或前一阶段]

阶段 2:[名称](并行)

  • 智能体 A:[agent-name]
    • 任务:[具体任务内容]
  • 智能体 B:[agent-name]
    • 任务:[具体任务内容]
  • 依赖项:阶段 1

阶段 3:汇总(Synthesis)

  • 结合阶段 2 的结果
  • 生成统一输出

协调原则(Coordination Rules)

  1. 先规划后执行 - 首先创建完整的执行计划
  2. 最小化交接 - 减少上下文切换(Context switching)
  3. 尽可能并行化 - 并行处理独立任务
  4. 明确边界 - 每个智能体(Agent)都有特定的职责范围
  5. 单一事实来源 - 每个产出物由一个智能体(Agent)负责

注意:复杂任务受益于多智能体编排。简单任务应直接使用单个智能体。

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.

  1. 5d ago First seen · 89 lines · 17 tokens per session scan A 68493e1e8fda

Subscribe to this mod's changes

orchestrate is a command published in the GitHub repository xu-xiang/everything-claude-code-zh (1,929 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 799 once invoked, about $0.0001 per session on Opus 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-08-30.