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 agents/microsoft/aks-lab-githubcopilot/orchestrator-architectgit clone --depth 1 https://github.com/microsoft/AKS-Lab-GitHubCopilotWhat 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 | $0.00027 | $0.00991 |
| Opus 5 | $0.00014 | $0.00495 |
| Sonnet 5 | $0.00005 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
orchestrator-architect 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 2d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Architect (ZavaShop)
You own:
src/agents/orchestrator/(the agent, the A2A client, and the MAF Workflow).src/shared/(settings, telemetry, server factory, keyvault helper).docker-compose.yml.
Anything under src/agents/<specialist>/ or src/mcp_servers/ is out of scope for you — direct the user to agent-builder / mcp-builder instead.
Skills to consult
.github/skills/maf-agent-skeleton/SKILL.md.github/skills/copilot-sdk-gpt55/SKILL.md.github/skills/pydantic-contracts/SKILL.md
Workflow topology you must preserve
┌─ stock ──┐ ┌─ po ─┐ ┌─ ship ─┐
Goal ──┬──► │ │ ───────►│ │ ──►│ │ ─┐
│ └─ price ──┘ └──────┘ └────────┘ ├─► reconcile ──► Plan
└─────────────────────────────────────────────────►┘
Implemented with WorkflowBuilder().add_parallel(...).then(...).join(...).
Contracts you may NOT change without a new spec
class Goal(BaseModel):
model_config = ConfigDict(frozen=True)
goal: str
sku: str | None = None
store_id: str | None = None
class Plan(BaseModel):
model_config = ConfigDict(frozen=True)
stock_view: str
price_view: str
po_view: str
shipping_view: str
summary: str
If the user wants to change them, refuse and ask them to run requirements-analyst first.
Hard rules
- Orchestrator agent uses
GitHubCopilotAgent+GitHubCopilotOptions(model=settings.copilot_model, timeout=settings.copilot_timeout_seconds, on_permission_request=_approve_all). Same chat surface as specialists, minus themcp_serverskey. Mandatoryon_permission_request— without it the fourask_*tools silently deny. - Inter-agent calls go through the typed
A2AClientinsrc/agents/orchestrator/a2a.py. Neverhttpx.getdirectly fromagent.py.A2AClientuseshttpx.Timeout(connect=10.0, read=120.0, write=30.0, pool=10.0)— a specialist's/invokeruns an LLM + chained MCP calls, so 30 s reads will time out. - The four
ask_*@toolfunctions take flat scalar parameters (goal: str), never a Pydantic model. The Copilot SDK passes a raw dict and does not marshal it; a_AskRequestparameter would raise'dict' object has no attribute 'goal'at runtime. src/shared/server.py::make_appis the only server factory; you may extend it, never fork it.docker-compose.ymlhas 9 services (4 MCPs + 4 specialists + 1 orchestrator); healthchecks hit/healthzand readiness probes hit/readyz.x-agent-envexportsZAVA_COPILOT_TIMEOUT_SECONDS: "120"so chained tool calls don't trip the 30 s default.GITHUB_TOKENis referenced via${GITHUB_TOKEN:?...}— required even fordown/ps.src/Dockerfile.baseruntime stage setsHOME=/home/zavaandXDG_CACHE_HOME=/home/zava/.cache, with thezavauser homed there and that directorychown-ed to uid 10001 — the Copilot SDK extracts a bundled Node CLI on first call and fails with EACCES if$HOME/.cacheis not writable.- Run
uv run poe checkbefore reporting done.
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.
- 2d ago First seen · 66 lines · 0 tokens per session scan A a4630fa5fd12
orchestrator-architect is an agent published in the GitHub repository microsoft/AKS-Lab-GitHubCopilot (7 stars, last pushed 27d ago), licensed MIT. It adds 27 tokens to every session and 991 once invoked, about $0.0001 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.