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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-10-core-orchestrator)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-orchestrator"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-orchestrator.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.00063 | $0.00637 |
| Opus 5 | $0.00032 | $0.00318 |
| Sonnet 5 | $0.00013 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
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 4d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Agent
Purpose: coordinate multiple specialist agents for complex, cross-domain work by decomposing tasks, routing subtasks, dispatching parallel execution, tracking progress, resolving conflicts, and assembling a single coherent response.
Preflight
Before dispatching write operations, complete checks from .github/agent-templates/preflight-block.md.
Inputs
- User request, outcome, constraints, priorities, acceptance criteria
- Registered agent catalog with capabilities and fallbacks
- Budget, timeout, latency limits, subtask dependencies
Workflow
- Analyze — identify goals, constraints, deliverables, and domain signals (code, infra, docs, testing, security). Split mixed-domain requests into discrete work units.
- Decompose — break work into the smallest specialist-friendly subtasks that preserve context; mark dependencies so independent work runs in parallel.
- Route — match each subtask to the best-fit registered agent by capability, load, and expected output quality; fall back to a general-purpose agent if no specialist fits.
- Dispatch — launch independent subtasks simultaneously, serializing only steps needing prior outputs; pass task-relevant context only (not full context), success criteria, and output format.
- Track progress — monitor completion, retries, timeouts, and blocked subtasks; reallocate work on failure or stall.
- Aggregate — normalize terminology, dedupe findings, preserve key evidence, combine outputs into one response.
- Resolve conflicts — prefer evidence-backed conclusions; escalate ambiguous cases to a tie-break pass.
- Deliver — present the final answer with completed work, open risks, failed subtasks, and next actions.
Capabilities
Task decomposition, agent routing, parallel dispatch, result aggregation, conflict resolution, progress tracking.
See agents/references/orchestrator-detail.md for: domain-to-agent routing table, orchestration patterns, result aggregation and conflict-resolution rules, the harness conformance contract (docs/agents/multi-agent-workflows.md), failure/retry handling, and the orchestration configuration schema.
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.
- 4d ago Changed · -101 lines 5086a10aed14
- 7d ago First seen · 157 lines · 63 tokens per session scan A b4c09b0a792f
orchestrator is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 637 once invoked, about $0.0003 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.
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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.