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/mathiasbourgoin/rosterWrote 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/plugins/mathiasbourgoin/roster/claude)<a href="https://agentmods.dev/plugins/mathiasbourgoin/roster/claude"><img src="https://agentmods.dev/badge/plugins/mathiasbourgoin/roster/claude/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/plugins/mathiasbourgoin/roster/claude"><img src="https://agentmods.dev/badge/plugins/mathiasbourgoin/roster/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
roster 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 15d 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.
What it actually says
{
"name": "roster",
"description": "Coordinated agent-team pipeline: recruiter + roster-* skills (question→research→intake→spec→plan→implement→review→qa→ship) + governance rules. Commands install as /roster:<name>.",
"version": "2.7.0",
"author": {
"name": "Mathias Bourgoin"
}
}
What it installs
The manifest is a name and a version. 40 commands, 8 agents travel with it, and installing the plugin installs all of them — 1,109 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command roster-review A 23 tokens
- Command recruit A 42 tokens
- Command roster-implement A 26 tokens
- Command roster-qa A 19 tokens
- Command roster-run A 18 tokens
- Command roster-ship A 19 tokens
- Command roster-spec A 27 tokens
- Command roster-init A 22 tokens
- Command roster-plan A 22 tokens
- Command roster-research A 25 tokens
- Command roster-skill-evolve A 23 tokens
- Command roster-skill-health A 15 tokens
- Command roster-upgrade A 29 tokens
- Command roster-audit A 20 tokens
- Command roster-intake A 18 tokens
- Command roster-question A 18 tokens
- Command roster-triage-critical A 23 tokens
- Command chamallaw-shadow A 37 tokens
- Command roster-formal-verify A 24 tokens
- Command roster-investigate A 21 tokens
- Command roster-spec-formal A 28 tokens
- Command roster-spec-infer A 27 tokens
- Command code-quality-auditor A 21 tokens
- Command image-generation A 21 tokens
- Command improvement-loop A 19 tokens
- Command improvement-loop-planner A 24 tokens
- Command team A 17 tokens
- Command chamallaw-feedback A 35 tokens
- Command kb-migrate A 21 tokens
- Command kb-reindex A 20 tokens
- Command roster-config A 15 tokens
- Command spec-compliance-auditor A 21 tokens
- Command ambiguity-auditor A 23 tokens
- Command git-conventions A 20 tokens
- Command harness-validator A 20 tokens
- Command kb-update A 21 tokens
- Command kb-search A 17 tokens
- Command tdd-workflow A 20 tokens
- Command roster-doctor B 25 tokens
- Command roster-workflow-build A 23 tokens
- Agent recruiter A 41 tokens
- Agent planner A 35 tokens
- Agent kb-agent A 25 tokens
- Agent architect A 20 tokens
- Agent implementer A 21 tokens
- Agent reviewer A 18 tokens
- Agent qa A 15 tokens
- Agent tech-lead A 25 tokens
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.
- 15d ago Changed fc7a015f0bb0
- 1mo ago First seen · 9 lines scan A 93ff2cc350c1
roster is a plugin published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.