What is agent-orchestration?

A policy for deciding whether a coding task should be done directly or given to a specialist agent. A specialist agent is a separate helper focused on a particular kind of work.

It is for choosing between inline work, delegation, or no delegation based on the task and the agents available in the project.

It reduces unnecessary delegation while identifying tasks where a specialist could improve planning, debugging, design, or review.

agent-orchestration — Skill for Claude Code by CassetteTapeCrackle

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.

Any agent

npx skills add CassetteTapeCrackle/claude-starters --skill agent-orchestration

Clone the repo

git clone --depth 1 https://github.com/CassetteTapeCrackle/claude-starters

Made for: Claude Code.

Or install claude-starters, the plugin that ships this one along with the rest of its 10 skills, 1 command, 8 agents, 2 hooks.

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/skills/cassettetapecrackle/claude-starters/agent-orchestration/github.svg)](https://agentmods.dev/skills/cassettetapecrackle/claude-starters/agent-orchestration)

Your own site

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

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 647 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.00059	$0.00647
Opus 5.5	$0.00024	$0.00259
Sonnet 5.5	$0.00012	$0.00129
Haiku 4.5	$0.00006	$0.00065

Measured 2mo ago against content hash a0ab448ded31, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-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 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.

skills/agent-orchestration/SKILL.md · 35 lines

How it starts

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

Agent orchestration (the dispatcher policy)

You are the orchestrator. You choose between doing work yourself and delegating to a specialist agent. Optimize for fewer tokens and better output — most of the time that means doing it yourself or skipping.

Candidates come from two channels

Reactive — the Stop hook surfaced a code-risk candidate (e.g. unsafe-auditor, rt-safety-auditor, any-eliminator) because changed code matched a risk pattern.
Proactive — the phase of the current task maps to a specialist:
- ideate → plugin-ideator / idea-brainstormer / competitor-analyst
- spec/plan → prd-writer / spec-critic
- research an unknown → deep-researcher
- design UI → ui-designer / ux-critic / plugin-ui-designer / design-system-author
- debug → debugger / regression-hunter
- audit quality → the per-stack auditors + starter-conformance-checker
- ship → technical-writer / release-copywriter / demo-script-writer / naming-agent

Only consider agents that actually exist for this project: the ones in .claude/agents/ (scoped) plus the global ones. Don't invent agents.

The decision — skip / inline / delegate

For each candidate, pick the cheapest option that gets the job done well:

SKIP if the agent's concern isn't really implicated, or the change is trivial (docs, a rename, a one-line tweak). This is the most common answer. Don't dispatch to prove diligence.
INLINE (do it yourself) if the surface is small and local (a few lines / one file) and you already have the context. Spinning a subagent would cost more than just doing it.
DELEGATE only when it clearly pays: a broad scan (many files / a whole module), work that would pull a lot into your context (isolation is the payoff — the subagent's tokens stay out of your window), or a well-scoped specialist job whose prompt does better than you would ad hoc.

Rules

Bias to skip/inline. When unsure and the surface is small, inline.
One agent at a time; don't chain speculative delegations. Delegate, read the result, then decide the next step.
Respect the project's own rules (its CLAUDE.md) — e.g. don't let an agent touch DSP on a non-DSP task.
After you've handled a surfaced candidate, don't re-evaluate the same unchanged diff.

Read the full file on GitHub · 35 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 · 35 lines · 59 tokens per session scan A a0ab448ded31

Subscribe to this mod's changes

agent-orchestration is a skill published in the GitHub repository CassetteTapeCrackle/claude-starters (1 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 647 once invoked, about $0.0002 per session on Opus 5.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-31.

Building agents Claude Code agentic-coding ai-agents anthropic boilerplate claude-code-plugin

agent-orchestration next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
agent-orchestrationCassetteTapeCrackle/claude-starters	Skill	1	4d ago	MIT	A	59	Claude Code
stack-prHigorAlves/orc	Skill	7	yesterday	MIT	A	52	Claude Code, Codex
systematic-debuggingHigorAlves/orc	Skill	7	yesterday	MIT	A	33	Claude Code
env-provisioningHigorAlves/orc	Skill	7	yesterday	MIT	A	66	Claude Code, Codex
state-protocolHigorAlves/orc	Skill	7	yesterday	MIT	A	47	Claude Code
browser-qaHigorAlves/orc	Skill	7	yesterday	MIT	A	42	Claude Code
evidence-publishHigorAlves/orc	Skill	7	yesterday	MIT	A	49	Claude Code, Codex