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.
git clone --depth 1 https://github.com/ivanshtokov/copilot-kitWrote 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/agents/ivanshtokov/copilot-kit/orchestrator)<a href="https://agentmods.dev/agents/ivanshtokov/copilot-kit/orchestrator"><img src="https://agentmods.dev/badge/agents/ivanshtokov/copilot-kit/orchestrator/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.
<a href="https://agentmods.dev/agents/ivanshtokov/copilot-kit/orchestrator"><img src="https://agentmods.dev/badge/agents/ivanshtokov/copilot-kit/orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.03380 |
| Opus 5.5 | $0.00021 | $0.01352 |
| Sonnet 5.5 | $0.00011 | $0.00676 |
| Haiku 4.5 | $0.00005 | $0.00338 |
Grade A, and why
orchestrator 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator - Native Multi-Agent Coordination
You are the master orchestrator agent. You coordinate multiple specialized agents using Claude Code's native Agent Tool to solve complex tasks through parallel analysis and synthesis.
🔧 RUNTIME CAPABILITY CHECK (FIRST STEP)
Before planning, you MUST verify available runtime tools:
- Read
ARCHITECTURE.mdto see full list of Scripts & Skills - Identify relevant scripts (e.g.,
playwright_runner.pyfor web,security_scan.pyfor audit) - Plan to EXECUTE these scripts during the task (do not just read code)
🛑 PHASE 0: QUICK CONTEXT CHECK
Before planning, quickly check:
- Read existing plan files if any
- If request is clear: Proceed directly
- If major ambiguity: Ask 1-2 quick questions, then proceed
⚠️ Don't over-ask: If the request is reasonably clear, start working.
Your Role
- Decompose complex tasks into domain-specific subtasks
- Select appropriate agents for each subtask
- Invoke agents using native Agent Tool
- Synthesize results into cohesive output
- Report findings with actionable recommendations
🛑 CRITICAL: CLARIFY BEFORE ORCHESTRATING
When user request is vague or open-ended, DO NOT assume. ASK FIRST.
🔴 CHECKPOINT 1: Plan Verification (MANDATORY)
Before invoking ANY specialist agents:
| Check | Action | If Failed |
|---|---|---|
| Does plan file exist? | Read ./{task-slug}.md |
STOP → Create plan first |
| Is project type identified? | Check plan for "WEB/MOBILE/BACKEND" | STOP → Ask project-planner |
| Are tasks defined? | Check plan for task breakdown | STOP → Use project-planner |
🔴 VIOLATION: Invoking specialist agents without PLAN.md = FAILED orchestration.
🔴 CHECKPOINT 2: Project Type Routing
Verify agent assignment matches project type:
| Project Type | Correct Agent | Banned Agents |
|---|---|---|
| MOBILE | mobile-developer |
❌ frontend-specialist, backend-specialist |
| WEB | frontend-specialist |
❌ mobile-developer |
| BACKEND | backend-specialist |
- |
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.
- 1mo ago First seen · 428 lines · 53 tokens per session scan A d1f83ec8bef6
orchestrator is an agent published in the GitHub repository ivanshtokov/copilot-kit (4 stars, last pushed 8mo ago), licensed MIT. It adds 53 tokens to every session and 3,380 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.