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 skills add dbc-oduffy/coordinator-claude --skill roadmap-planninggit 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/skills/dbc-oduffy/coordinator-claude/roadmap-planning)<a href="https://agentmods.dev/skills/dbc-oduffy/coordinator-claude/roadmap-planning"><img src="https://agentmods.dev/badge/skills/dbc-oduffy/coordinator-claude/roadmap-planning.svg" alt="Measured on agentmods" 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.00021 | $0.03616 |
| Opus 5 | $0.00010 | $0.01808 |
| Sonnet 5 | $0.00004 | $0.00723 |
| Haiku 4.5 | $0.00002 | $0.00362 |
Grade A, and why
roadmap-planning 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.
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 ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- residue/contact-points-checklist.md 1.8 KB
- residue/coordinator-resolutions-format.md 192 B
- residue/downstream-mechanisms.md 5.0 KB
- residue/entry-points-b-c-d.md 5.2 KB
- residue/peer-team-ask-format.md 485 B
- residue/research-depth-assessment.md 2.6 KB
- residue/stub-frontmatter-schema-and-field-notes.md 10.0 KB
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 Changed · +7 lines 0efb98fcaade
- 3d ago Changed · +11 lines 3f1bb2f35a8e
- 5d ago First seen · 193 lines · 21 tokens per session scan A ecf5b6f57b18
roadmap-planning is a skill published in the GitHub repository dbc-oduffy/coordinator-claude (5 stars, last pushed yesterday), with no licence file. It adds 21 tokens to every session and 3,616 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
tech-lead
Channel operator (IRC handle @techlead) for the mARC agent team. Compiles chat demands into ready-to-execute work, records them on the GitHub Project board/Issues, and dispatches to specialists (@dev, @sre, @design, @sec, @rev, @research). Invoke with /tech-lead to turn discussion into tracked, delegated tasks.
init
Opt-in onboarding for the mARC agent team. Scaffolds a per-repo team binding so the team graduates from ephemeral session-memory to persistent, versioned config — without ever writing a file silently. Discovers the repo's org/repo/ project at runtime via gh, prefills {{ agentsdir }}/team.toml, and (optionally) a lean…
matilha-hunt
Use when user is ready to dispatch a wave's subprojects — creates git worktrees and kickoff.md per SP, writes wave-NN-status.md, prints dispatch commands.
matilha-init
Use when starting a new project or initializing Matilha in an existing one — scaffolds project-status.md, AGENTS.md, CLAUDE.md/GEMINI.md, and phase 0 artifacts.
matilha-howl
Use when user asks about project state, current phase, active waves, or next action — reads project-status.md and surfaces the status in a stream-friendly format.
matilha-review
Use when user wants a quality review of a completed wave — will dispatch 6 parallel review agents (code-quality, UX, security, architecture, performance, docs) once Wave 3c ships.