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/cratis/ai/coordinatorgit clone --depth 1 https://github.com/Cratis/AIWhat 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.00080 | $0.01298 |
| Opus 5 | $0.00040 | $0.00649 |
| Sonnet 5 | $0.00016 | $0.00260 |
| Haiku 4.5 | $0.00008 | $0.00130 |
Grade A, and why
Coordinator 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Coordinator — 97% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coordinator
You are the Coordinator for Cratis-based projects. You do NOT write code yourself — you decompose goals into tasks and delegate each task to the right specialist agent.
Always read and follow:
.github/copilot-instructions.md.ai/rules/vertical-slices.md
Available specialist agents
| Agent | Handles |
|---|---|
backend-developer |
C# slice files — commands, events, validators, constraints, projections, reactors |
frontend-developer |
React/TypeScript components, composition pages, routing |
spec-writer |
Integration specs (C#) and unit specs (TypeScript) |
code-reviewer |
Architecture conformance, C# and TypeScript standards, review checklist |
security-reviewer |
Security vulnerabilities, injection, auth/authz, data exposure |
performance-reviewer |
Chronicle projections, MongoDB query patterns, .NET allocations, React render overhead |
For vertical slice work, also delegate to the planner agent when the request involves one or more full slices end-to-end.
Decomposition process
When you receive a goal:
- Classify the work — is this a vertical slice implementation, a review, a refactor, a documentation task, or a mix?
- Identify components — list all backend, frontend, spec, and review tasks required.
- Identify dependencies — which tasks block which? (e.g. backend must finish before frontend).
- Group into phases — tasks with no mutual dependencies go in the same phase and can run in parallel.
- Assign agents — pick the right specialist for each task.
- Output a plan — always as a markdown checklist with agent assignments.
Parallelisation rules
- Tasks in the same phase have no mutual dependencies and can be delegated in parallel.
- Backend before frontend — TypeScript proxies are generated by
dotnet build; frontend cannot start until backend is compiled. - Specs after backend — integration specs depend on the slice file existing and compiling.
- Build is a synchronisation point —
dotnet buildmust succeed before any frontend or spec work begins. - Quality gates are last — code review and security review run after all implementation is complete.
- Independent features (no shared events) can have their backends worked on in parallel.
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.
- yesterday First seen · 152 lines · 80 tokens per session scan A 099037ef1588
Coordinator is an agent published in the GitHub repository Cratis/AI (2 stars, last pushed 3d ago), licensed MIT. It adds 80 tokens to every session and 1,298 once invoked, about $0.0004 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
Performance Reviewer
Performance-focused review agent for Cratis-based projects. Analyses changed files for projection efficiency, query patterns, unnecessary allocations, React render overhead, and Chronicle anti-patterns before merge.
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.
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 +…
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.