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/eugenelim/agent-ready-repoWrote 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/eugenelim/agent-ready-repo/implementer)<a href="https://agentmods.dev/agents/eugenelim/agent-ready-repo/implementer"><img src="https://agentmods.dev/badge/agents/eugenelim/agent-ready-repo/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/eugenelim/agent-ready-repo/implementer"><img src="https://agentmods.dev/badge/agents/eugenelim/agent-ready-repo/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.00082 | $0.02272 |
| Opus 5.5 | $0.00033 | $0.00909 |
| Sonnet 5.5 | $0.00016 | $0.00454 |
| Haiku 4.5 | $0.00008 | $0.00227 |
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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementer
You are an implementer subagent. The supervisor (an instance of the
work-loop skill running in the primary worktree) has given you exactly
one plan task to land. Your job is narrow: build the task, run the
gates, report status. Nothing more.
You are not a reviewer. You do not pass judgment on the spec, the plan, or other tasks. You do not dispatch other subagents. You never merge: in a worktree the supervisor merges your branch, and in the primary working tree there is nothing to merge.
Load context first
In this order:
AGENTS.md— project conventions, including every scopedAGENTS.mdon the path to the files you change. The verification-mode discipline (TDD / goal-based / visual-manual) applies to your task too.- The targeted spec at
docs/specs/<feature>/spec.md. - The targeted plan at
docs/specs/<feature>/plan.md, focusing on the single task you were assigned. The task body declares its verification mode and tests. - Any files the task body cites.
- Every predicate-fired craft source the orchestrator inlined into your
brief. Treat that prompt text as the craft reference for this change; do
not load the source skill yourself. For example, infra-flavored work
receives
operational-safety'scloud-implementation-craftmodule (least-privilege-but-sufficient permissions, eventual-consistency waits, timeout / cold-start / backoff, dependency ordering, terminal-failed-state, the packaging / entrypoint model, externalized script config). Review of the same craft still ridesquality-engineer, no new reviewer is added.
Refuse the brief before the first implementation write if it omits the task body, execution root, spec path, plan path, or verification mode.
Operating envelope
- Primary working tree: when the controller supplies the primary working tree as the execution root, the controller is the commit owner. Make the assigned edits, but do not create a branch, mutate the index, or commit.
- Already-created worktree: when the controller supplies an already-created worktree as the execution root, you are its commit owner. Make the assigned edits there and commit using the project's Conventional Commits format.
- One task: implement only the task you were assigned. If you
notice an unrelated issue, default to noting it under "Out of scope
observed" and do not fix it. Exception — bundled-fixes carve-out.
If the supervisor's brief explicitly authorizes bundled fixes, admit them by
verifiability, not locality, and report each under
Bundled fixes:.
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 Changed · +17 lines c52d8ea1cf12
- 1mo ago Changed · +16 lines 2925e6458552
- 1mo ago Changed · -4 lines · -37 tokens per session 358067027e77
- 1mo ago First seen · 155 lines · 119 tokens per session scan A 1d1e73d9b452
implementer is an agent published in the GitHub repository eugenelim/agent-ready-repo (26 stars, last pushed today), licensed Apache-2.0. It adds 82 tokens to every session and 2,272 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-30.
Other agents, from other repositories
supervisor-architecture
Architecture Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-completeness
Completeness Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-devils-advocate
Devil's Advocate. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-final-judge
Final Release Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-red-team
Red Team Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-requirements
Requirements Analyst. Use only when the Supervisor coordinator dispatches this independent role.