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/dbc-oduffy/coordinator-claudeWrote 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/dbc-oduffy/coordinator-claude/apm)<a href="https://agentmods.dev/agents/dbc-oduffy/coordinator-claude/apm"><img src="https://agentmods.dev/badge/agents/dbc-oduffy/coordinator-claude/apm/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/dbc-oduffy/coordinator-claude/apm"><img src="https://agentmods.dev/badge/agents/dbc-oduffy/coordinator-claude/apm.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.00034 | $0.03051 |
| Opus 5.5 | $0.00014 | $0.01220 |
| Sonnet 5.5 | $0.00007 | $0.00610 |
| Haiku 4.5 | $0.00003 | $0.00305 |
Grade A, and why
apm 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 4d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 4d ago Changed · +8 lines 2a1d1602d68b
- 9d ago Changed · +6 lines d31e44fc1426
- 12d ago Changed · +1 lines c888043f5c9b
- 17d ago Changed · -106 lines · -7 tokens per session 393872dcae70
- 20d ago Changed · -2 lines 259d6a24a0ff
- 21d ago Changed · -2 tokens per session fc2755e31406
- 23d ago Changed · +1 lines 3ec127a5d463
- 24d ago Changed · -1 lines bc6758543e12
- 1mo ago Changed · -19 lines c29491ea2041
- 1mo ago First seen · 328 lines · 43 tokens per session scan A 08b3c639c60a
apm is an agent published in the GitHub repository dbc-oduffy/coordinator-claude (6 stars, last pushed 3d ago), with no licence file. It adds 34 tokens to every session and 3,051 once invoked, about $0.0001 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
engineering-manager
The Engineering Manager of the aSPARK team. Use in the Plan phase (/sprint-plan) to turn an approved spec into a technical plan: architecture decision with rejected alternatives, ordered task breakdown, test strategy and risks. Also use when a plan must be revised after review or QA findings.
review
Correctness/quality review specialist (IRC handle @rev) dispatched to audit pull requests and branch diffs for bugs, regressions, and maintainability issues before code merges, alongside @sec's security pass.
security
Security review specialist (IRC handle @sec) dispatched to audit pull requests and branch diffs for security vulnerabilities before code merges.
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
sre
Site Reliability Engineer specialist (IRC handle @sre) dispatched for deployment pipeline management, infrastructure health audits, incident response, backups, and cost optimization.
design
Design and front-end specialist (IRC handle @design) dispatched to create, refine, and validate user interface layouts and end-to-end user experience flows.