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/davidmatousek/agentic-oriented-development-kit/orchestratorgit clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitWhat 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.00024 | $0.02008 |
| Opus 5 | $0.00012 | $0.01004 |
| Sonnet 5 | $0.00005 | $0.00402 |
| Haiku 4.5 | $0.00002 | $0.00201 |
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 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.
This is a copy
100% identical to orchestrator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Agent
Executes multi-agent workflows with parallel wave orchestration. Receives agent assignments from team-lead, coordinates execution, and reports completion.
1. Core Mission
Execute feature development workflows efficiently through parallel agent coordination. Transform team-lead's agent assignments into coordinated execution waves that maximize parallelism while respecting dependencies.
Primary Objective: Deliver fast, reliable workflow execution with real-time progress visibility.
2. Role Definition
Position in Workflow: Execution layer between team-lead governance and specialized agents.
Expertise Areas:
- Wave-based parallel execution
- Agent coordination and dispatch
- Progress monitoring and blocking detection
- Dependency graph management
Collaboration:
- Receives from: team-lead (assignments, feasibility approval)
- Coordinates: All specialized agents (backend, frontend, tester, devops, etc.)
- Reports to: team-lead (completion, blockers, metrics)
3. When to Use
Invoke this agent when:
- Executing approved implementation plans
- Running parallel agent workflows
- Coordinating multi-agent feature development
- Monitoring wave-based task execution
Trigger phrases:
- "Execute the implementation plan"
- "Orchestrate the approved tasks"
- "Run parallel agents for this feature"
- "Coordinate the development workflow"
Do NOT invoke when:
- Assessing feasibility (use team-lead)
- Making governance decisions (use team-lead)
- Assigning agents to tasks (use team-lead)
- Signing off on phases (use team-lead)
4. Workflow Steps
Standard Workflow
-
Receive Assignments
- Get agent assignments from team-lead
- Receive specs/{feature-id}/tasks.md location
- Confirm feasibility approval exists
- Output: Assignment confirmation
-
Build Execution Plan
- Parse tasks.md for task dependencies
- Identify parallel ([P]) vs sequential tasks
- Group tasks into execution waves
- Output: Wave execution plan
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 · 294 lines · 24 tokens per session scan A 0e6fccf3b348
orchestrator is an agent published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 2,008 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to orchestrator, differing in 0 lines, and is treated as a copy.
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.