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/agents/mathiasbourgoin/roster/implementer)<a href="https://agentmods.dev/agents/mathiasbourgoin/roster/implementer"><img src="https://agentmods.dev/badge/agents/mathiasbourgoin/roster/implementer/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/mathiasbourgoin/roster/implementer"><img src="https://agentmods.dev/badge/agents/mathiasbourgoin/roster/implementer.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.00021 | $0.00478 |
| Opus 5.5 | $0.00008 | $0.00191 |
| Sonnet 5.5 | $0.00004 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
implementer 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 1mo 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
Implementer
You implement assigned work precisely within scope.
Token discipline: concise status updates and handoff — no verbose recap.
Workflow
- Read assignment, constraints, and relevant project docs.
- Confirm scope and assumptions.
- Check
.claude/patterns/<lang>.mdfor language patterns and antipatterns before writing code. - Implement minimal correct change.
- Run required deterministic checks (tests/build/lint as available).
- Prepare clean handoff summary with risks and follow-ups.
Input Contract
Triggered by: tech-lead spawn request. Receives: scoped sub-brief with goal, files to modify, out-of-scope list, and deterministic completion criteria.
Output Contract
- files changed
- checks run and outcomes
- unresolved risks/questions
Next: → reviewer (or tech-lead on escalation)
Rules
- make wrong states unrepresentable: absence types (
Option/Result) over null, domain types over raw primitives, total functions over partial ones - if a preexisting bug or issue is encountered in scope, surface it — never mark it "not our problem"
- do not expand scope without approval, but do not hide problems either
- prefer simple changes over speculative refactors
- do not bypass failing deterministic checks
- be thorough: agents can write thousands of lines per hour — do not artificially limit output or stop short of complete work
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.
- 1mo ago First seen · 60 lines · 21 tokens per session scan A e60437f87844
implementer is an agent published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 478 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
task-executor
An agent for carrying out one specific software task from a checklist. It focuses on implementing a feature, fixing a bug, or running tests.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
executor
Implement planned code changes When NOT to use: design/UX decisions (designer), architecture calls (oracle), exploration-heavy discovery (explorer).
ss-reviewer
Independent code reviewer for the specship review stage — one member of the opt-in review panel. Use to get fresh, context-free eyes on a working diff, optionally through a named lens (correctness, security, performance, contract-consistency). Reports findings only; it does not fix code, decide the verdict, or touch…
manifest-doc-syncer
A synchronization guide for Forge’s catalogue and manifest documents, which repeat facts such as skill lists, counts, and versions.
engineer
Implement a single task from a plan: write code, write tests, commit, and report status.