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.
npx agentmods add commands/evan043/claude-cli-advanced-starter-pack/orchestration-guide.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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.
[](https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/orchestration-guide.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/orchestration-guide.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/orchestration-guide.template.svg" alt="Measured on agentmods" height="20"></a>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.01354 |
| Opus 5 | $0.00000 | $0.00677 |
| Sonnet 5 | $0.00000 | $0.00271 |
| Haiku 4.5 | $0.00000 | $0.00135 |
Grade B, and why
orchestration-guide.template scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
tail -50 .claude/logs/orchestrator-audit.jsonl | jq . How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
orchestration-guide — Codex Runtime
This guide describes Claude Code CLI's multi-agent orchestration patterns using Task(). These patterns are Claude Code CLI-specific.
Codex Equivalent Patterns
In Codex, orchestration is done through:
- Sequential steps — work through tasks one by one in a single conversation
- File-based state — save progress to JSON files between steps
- Explicit handoffs — write completion summaries to files for next steps
The core orchestration concepts (phases, epics, roadmaps) are the same. Only the execution mechanism differs.
For learning about CCASP orchestration concepts (applicable to both runtimes), I'll explain the patterns. Tell me what you want to understand.
description: Agent orchestration patterns guide model: haiku
Agent Orchestration Guide
Quick reference for executing phased development plans with hierarchical agent orchestration.
Agent Hierarchy
L1 Orchestrator (You/Main)
├── L2 Frontend Specialist
│ ├── L3 Component Search Worker
│ ├── L3 Style Analyzer Worker
│ └── L3 Test Generator Worker
├── L2 Backend Specialist
│ ├── L3 API Discovery Worker
│ └── L3 Schema Validator Worker
├── L2 Testing Specialist
│ └── L3 Coverage Analyzer Worker
└── L2 Deployment Specialist
└── L3 Config Validator Worker
Spawning Agents
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.
- 6d ago First seen · 192 lines · 0 tokens per session scan B ac94895e22b1
orchestration-guide.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,354 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
release-harn
Run the tag-first Harn release workflow.
discover
Search the Everruns(Dev) API catalog for available operations.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.