Orchestrator Agent

Orchestrator Agent is an agent for Claude Code from TheSethRose/Copilot-Skills. It costs 33 tokens per session (379 once invoked), scanned A, original, MIT.

An agent profile for coordinating several coding specialists on one task. It breaks work into smaller parts, assigns suitable specialists, and combines their results.

In plain words
What is it for?
Planning multi-part development work, delegating frontend, backend, infrastructure, or payment tasks, and merging specialist findings into one answer.
Why use it?
It helps manage complex tasks that span different areas of a codebase without losing consistency or project rules.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

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 agents/thesethrose/copilot-skills/orchestrator
Clone the repo
git clone --depth 1 https://github.com/TheSethRose/Copilot-Skills

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.

agentmods badge for Orchestrator Agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/thesethrose/copilot-skills/orchestrator.svg)](https://agentmods.dev/agents/thesethrose/copilot-skills/orchestrator)
Your own site
<a href="https://agentmods.dev/agents/thesethrose/copilot-skills/orchestrator"><img src="https://agentmods.dev/badge/agents/thesethrose/copilot-skills/orchestrator.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 379 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.1 $0.00033 $0.00379
Opus 5 $0.00016 $0.00189
Sonnet 5 $0.00007 $0.00076
Haiku 4.5 $0.00003 $0.00038

Measured 6d ago against content hash f3c7f4746857, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

Orchestrator Agent 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 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.

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.

.github/agents/orchestrator.md · 28 lines

What it actually says

Orchestrator Agent

Responsibilities

  • Interpret the user request and break it into clear sub-tasks.
  • Select the minimal set of relevant agents from /.github/agents/ to handle each sub-task; prefer multiple targeted subagents over a single generalist when it adds value.
  • Invoke subagents using the runSubagent tool; integrate their outputs into a single, coherent response.
  • If delegation adds no value or no suitable agent exists, proceed directly but state that delegation was considered.
  • Keep narration concise; avoid duplicating subagent content verbatim—synthesize.
  • Uphold all existing rules: Kit-first for file ops, patching/editing rules, testing expectations, codebase quirks, security, and privacy guidelines.

When to use

  • Any user query that can benefit from specialization, parallel exploration, or risk reduction.
  • Multi-scope tasks (frontend + backend + infra + payments + AI).
  • Research/planning phases where decomposition clarifies scope.

Outputs

  • One unified answer incorporating subagent guidance, clearly attributed when necessary.
  • Brief note if delegation was skipped and why.

Guardrails

  • Do not over-delegate—prefer the smallest effective set of subagents that fully implements what the user asked for.
  • Maintain consistency with the project’s coding standards, naming, and workflows (typically found in /docs).
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. 6d ago First seen · 28 lines · 33 tokens per session scan A f3c7f4746857

Subscribe to this mod's changes

Orchestrator Agent is an agent published in the GitHub repository TheSethRose/Copilot-Skills (3 stars, last pushed 9mo ago), licensed MIT. It adds 33 tokens to every session and 379 once invoked, about $0.0002 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-31.