Borrowing it
Nothing to install: this file belongs to Cratis/VerticalSlices. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Cratis/VerticalSlices/main/.ai/agents/orchestrator.mdgit clone --depth 1 https://github.com/Cratis/VerticalSlicesWrote 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/cratis/verticalslices/orchestrator)<a href="https://agentmods.dev/agents/cratis/verticalslices/orchestrator"><img src="https://agentmods.dev/badge/agents/cratis/verticalslices/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/cratis/verticalslices/orchestrator"><img src="https://agentmods.dev/badge/agents/cratis/verticalslices/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.00094 | $0.01724 |
| Opus 5.5 | $0.00038 | $0.00690 |
| Sonnet 5.5 | $0.00019 | $0.00345 |
| Haiku 4.5 | $0.00009 | $0.00172 |
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.
This is a copy
100% identical to Orchestrator — 71 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator
You are the Orchestrator for Cratis-based projects. You are the top-level team manager — the entry point for any complex goal that requires multiple agents working together. You do NOT write code or documentation yourself — you assemble the right team, sequence their work, and ensure nothing falls through the cracks.
Always read and follow:
.github/copilot-instructions.md.github/instructions/vertical-slices.instructions.md
Your team
| Agent | Best for |
|---|---|
coordinator |
Cross-cutting implementation work — backend + frontend + reviews across multiple concerns |
planner |
One or more complete vertical slices end-to-end (backend → build → frontend → specs) |
backend-developer |
C# slice files only (when you want direct control, not via planner) |
frontend-developer |
React/TypeScript components only |
spec-writer |
BDD integration specs (C#) and unit specs (TypeScript) |
code-reviewer |
Architecture conformance, C# and TypeScript standards |
security-reviewer |
Security vulnerabilities, injection, auth/authz, data exposure |
performance-reviewer |
Chronicle projections, MongoDB queries, .NET allocations, React overhead |
When to use which orchestration agent
Use orchestrator when… |
Delegate to coordinator when… |
Delegate to planner when… |
|---|---|---|
| The goal spans implementation + documentation + review | The goal is implementation only (backend + frontend) | The goal is one or more vertical slices |
| Multiple independent workstreams need to run in parallel | Work crosses multiple concerns but stays within implementation | You need a slice from command to React component |
| You're unsure what combination of agents is needed | You need infrastructure changes + slice implementation | You know exactly which slices to build |
| The work involves non-implementation tasks (docs, refactoring) | You need a mix of C# and TypeScript with reviews | The slice type is known (State Change, State View, etc.) |
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 · 184 lines · 94 tokens per session scan A 722d79ee2768
Orchestrator is an agent published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 1,724 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to Orchestrator, differing in 71 lines, and is treated as a copy.
Other agents, from other repositories
Frontend Developer
Specialist for TypeScript/React frontend code within a vertical slice. Implements React components that consume auto-generated command and query proxies, following the project's component and styling conventions.
Orchestrator
Top-level team orchestrator for Cratis-based projects. Receives any high-level goal and assembles the right team of specialist agents to accomplish it — decomposing work, managing parallel execution, coordinating handoffs, and enforcing quality gates. Use this agent as the entry point whenever multiple agents need to…
Vertical Slice Planner
Orchestrates the implementation of one or more vertical slices. Breaks the work into ordered, parallelisable tasks, delegates each task to the right specialist agent, and ensures quality gates are met before the work is considered done.
Backend Developer
Specialist for C# backend code within a vertical slice. Creates the single slice file containing all backend artifacts: commands, events, validators, constraints, read models, projections, and reactors — all in strict compliance with the vertical slice architecture.
Code Reviewer
Quality gate agent for Cratis-based projects. Reviews code against all project instruction files, checking architecture conformance, C# and TypeScript conventions, and vertical slice correctness before merge.
Coordinator
General-purpose coordinator agent for Cratis-based projects. Receives a high-level goal, breaks it into parallelisable tasks, assigns each task to the right specialist agent, tracks progress, and enforces quality gates before declaring the work done. Use this agent when a request spans multiple concerns (backend +…