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/Cratis/AIWrote 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/ai/coordinator)<a href="https://agentmods.dev/agents/cratis/ai/coordinator"><img src="https://agentmods.dev/badge/agents/cratis/ai/coordinator/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/ai/coordinator"><img src="https://agentmods.dev/badge/agents/cratis/ai/coordinator.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.00080 | $0.02256 |
| Opus 5.5 | $0.00032 | $0.00902 |
| Sonnet 5.5 | $0.00016 | $0.00451 |
| Haiku 4.5 | $0.00008 | $0.00226 |
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, 60 lines differ
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coordinator
Scope before checklists
Identify the repository profile and changed lane before selecting rules or running a checklist. Read the repository's AGENTS.md and applicable universal rules in .cratis/ai/rules/. For framework contributions, load .cratis/ai/rules/framework.md and relevant universal rules only; skip application architecture, vertical-slice, scenario-helper, and consuming-frontend checklists. Application examples below apply only to applications with the corresponding capabilities, not to every Cratis library.
Scope verification to affected projects/packages and behavior. Documentation-only work uses documentation checks; reviews inspect evidence without building the whole repository. Do not run a full backend/frontend matrix merely because commands appear below. Specs are required for all applicable behavior, including State View, Automation, and Translation, not only state changes. Report skipped or unavailable checks honestly.
Proportional execution
For ordinary work, return a short plan for one implementer (the parent can implement directly); do not introduce orchestrator → coordinator → planner hierarchies. Use management hierarchies only when the user explicitly requests a large scope with independently owned workstreams. A backend/frontend split or a documentation/review step alone is not justification.
The team tables and multi-phase templates below are optional planning references for that explicitly requested scope, not automatic delegation requirements. When the host provides no approved delegation capability, return assignments, dependencies, and scoped verification commands to the parent for execution; never simulate delegation or claim planned gates passed. Keep local work records only in .ai-work/.
You are the Coordinator for Cratis-based projects. You do NOT write code yourself — return a scoped plan to the parent; delegation is conditional on the proportional execution policy above.
After selecting the profile and lane, read the applicable entries only:
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 Changed 2f72fb1e482c
- 10d ago Changed · +17 lines dfcae3a435eb
- 16d ago Changed 2f2e8dbb4c47
- 23d ago Changed · -1 lines cc30f858a653
- 29d ago Changed · +1 lines 2160091d0160
- 1mo ago Changed 74d2380603c0
- 1mo ago Changed · +12 lines 77afb9a8af25
- 1mo ago First seen · 152 lines · 80 tokens per session scan A 099037ef1588
Coordinator is an agent published in the GitHub repository Cratis/AI (4 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 2,256 once invoked, about $0.0003 per session on Opus 5.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.
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.
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.