A command that runs several coding agents in sequence, passing each agent’s findings to the next. It supports workflows for features, bug fixes, refactoring, and security reviews.

Use it for complex feature work, debugging, safe refactoring, or security-focused review. Each workflow combines agents such as planners, test-guided developers, code reviewers, architects, and security reviewers.

It coordinates related review and implementation steps so you do not have to invoke each specialist or transfer context manually.

orchestrate — Command by zhmxiaowo

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/zhmxiaowo/opencode-simple/orchestrate

Clone the repo

git clone --depth 1 https://github.com/zhmxiaowo/opencode-simple

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

When invoked 804 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 91% copy Near-identical to another mod 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	$0.00014	$0.00804
Opus 5	$0.00007	$0.00402
Sonnet 5	$0.00003	$0.00161
Haiku 4.5	$0.00001	$0.00080

Measured yesterday against content hash 3f8657ad0abb, 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 yesterday.

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.

Origin

This is a copy

91% identical to orchestrate — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.opencode/commands/orchestrate.md · 177 lines

How it starts

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

Orchestrate Command

Sequential agent workflow for complex tasks.

Usage

/orchestrate [workflow-type] [task-description]

Workflow Types

feature

Full feature implementation workflow:

planner -> tdd-guide -> code-reviewer -> security-reviewer

bugfix

Bug investigation and fix workflow:

planner -> tdd-guide -> code-reviewer

refactor

Safe refactoring workflow:

architect -> code-reviewer -> tdd-guide

security

Security-focused review:

security-reviewer -> code-reviewer -> architect

Execution Pattern

For each agent in the workflow:

Invoke agent with context from previous agent
Collect output as structured handoff document
Pass to next agent in chain
Aggregate results into final report

Handoff Document Format

Between agents, create handoff document:

## HANDOFF: [previous-agent] -> [next-agent]

### Context
[Summary of what was done]

### Findings
[Key discoveries or decisions]

### Files Modified
[List of files touched]

### Open Questions
[Unresolved items for next agent]

### Recommendations
[Suggested next steps]

Example: Feature Workflow

/orchestrate feature "Add user authentication"

Executes:

Planner Agent
- Analyzes requirements
- Creates implementation plan
- Identifies dependencies
- Output: HANDOFF: planner -> tdd-guide
TDD Guide Agent
- Reads planner handoff
- Writes tests first
- Implements to pass tests
- Output: HANDOFF: tdd-guide -> code-reviewer
Code Reviewer Agent
- Reviews implementation
- Checks for issues
- Suggests improvements
- Output: HANDOFF: code-reviewer -> security-reviewer
Security Reviewer Agent
- Security audit
- Vulnerability check
- Final approval
- Output: Final Report

Final Report Format

ORCHESTRATION REPORT
====================
Workflow: feature
Task: Add user authentication
Agents: planner -> tdd-guide -> code-reviewer -> security-reviewer

SUMMARY
-------
[One paragraph summary]

AGENT OUTPUTS
-------------
Planner: [summary]
TDD Guide: [summary]
Code Reviewer: [summary]
Security Reviewer: [summary]

FILES CHANGED
-------------
[List all files modified]

TEST RESULTS
------------
[Test pass/fail summary]

SECURITY STATUS
---------------
[Security findings]

RECOMMENDATION
--------------
[SHIP / NEEDS WORK / BLOCKED]

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

yesterday First seen · 177 lines · 14 tokens per session scan A 3f8657ad0abb

Subscribe to this mod's changes

orchestrate is a command published in the GitHub repository zhmxiaowo/opencode-simple (2 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 804 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to orchestrate, differing in 6 lines, and is treated as a copy.

Code review Debugging Testing

orchestrate