A command that runs a sequence of specialized agents for a complex software task.

It supports workflows for new features, bug fixes, refactoring, and security-focused work, passing each agent's findings to the next one and producing a final report.

It organizes planning, implementation checks, testing guidance, code review, and security review so important steps are not overlooked.

orchestrate — Command for Claude Code by joneqian/claude-skills-suite

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/joneqian/claude-skills-suite

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/joneqian/claude-skills-suite/orchestrate/github.svg)](https://agentmods.dev/commands/joneqian/claude-skills-suite/orchestrate)

Your own site

<a href="https://agentmods.dev/commands/joneqian/claude-skills-suite/orchestrate"><img src="https://agentmods.dev/badge/commands/joneqian/claude-skills-suite/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/joneqian/claude-skills-suite/orchestrate"><img src="https://agentmods.dev/badge/commands/joneqian/claude-skills-suite/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 787 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.00000	$0.00787
Opus 5.5	$0.00000	$0.00315
Sonnet 5.5	$0.00000	$0.00157
Haiku 4.5	$0.00000	$0.00079

Measured 2mo ago against content hash a9d8de11e90a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

orchestrate — 100% identical, 0 lines differ
orchestrate — 100% identical, 2 lines differ
orchestrate — 91% identical, 6 lines differ

commands/orchestrate.md · 173 lines

How it starts

The opening of the file, as written. The whole thing — 173 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:

explorer -> 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 · 173 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.

2mo ago First seen · 173 lines · 0 tokens per session scan A a9d8de11e90a

Subscribe to this mod's changes

orchestrate is a command published in the GitHub repository joneqian/claude-skills-suite (32 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 787 tokens. 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-31.

Building agents Planning

orchestrate next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
orchestratejoneqian/claude-skills-suite	Command	32	9mo ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code