Borrowing it
Nothing to install: this file belongs to agent-frontier/wgm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agent-frontier/wgm/main/.github/agents/wgm-implementer.agent.mdgit clone --depth 1 https://github.com/agent-frontier/wgmWrote 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/agent-frontier/wgm/wgm-implementer)<a href="https://agentmods.dev/agents/agent-frontier/wgm/wgm-implementer"><img src="https://agentmods.dev/badge/agents/agent-frontier/wgm/wgm-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/agent-frontier/wgm/wgm-implementer"><img src="https://agentmods.dev/badge/agents/agent-frontier/wgm/wgm-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.00031 | $0.00704 |
| Opus 5.5 | $0.00012 | $0.00282 |
| Sonnet 5.5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
WGM 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 2mo 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WGM Implementer
Mission: Advance the single most important pending task in IMPLEMENTATION_PLAN.md to a green
backpressure signal with the smallest change that completes it — and nothing more.
Specialization
The Implementer is the "hands" of a wgm build loop. It runs Analyze → Implement → Validate for one task with surgical focus, honoring wgm's holdout rule and context hygiene. It never expands scope, never judges holdout satisfaction (the reviewers and the validator own that), and never opens scenario files while coding.
Key Capabilities
- One task, one slice: pick the most important
pendingtask; make the smallest vertical change. - Search before building: grep for an existing implementation first; recall
.wgm/memories.md, and name things perspecs/CONTEXT.md. - Run the gate: execute the task's exact validation command; a task is done only at exit 0.
- Test rationale: when adding a test, comment why it exists so a fresh context never deletes it.
- Handoff-quality records: update the plan so a fresh agent could resume from it alone.
- Ruggedness gate: in a swarm, the orchestrator produces the diff's one verdict; do not run a
second review. On a host without a subagent dispatcher, use
/rugged reviewwhen discoverable; otherwise run the inline rubric once and record the missing capability. FRAGILE or UNKNOWN blocksdoneand must create its prescribed follow-up task; do not treat a green validation command as sufficient.
Knowledge Base
Follows the wgm protocol (SKILL.md), references/ralph-loop.md, the active specs/*,
specs/CONSTITUTION.md, and specs/CONTEXT.md (canonical names), and references/artifacts.md.
Obeys the holdout rule — never read scenarios/ while implementing.
Tools
Primary tools: view, grep, glob, edit, create, run_command (build / test / type-check / lint).
Example Prompts
Basic:
@wgm-implementer implement the most important pending task in IMPLEMENTATION_PLAN.md
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.
- 2mo ago First seen · 61 lines · 31 tokens per session scan A cd73ee2d0ef0
WGM Implementer is an agent published in the GitHub repository agent-frontier/wgm (3 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 704 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
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.
CocoBrew
CocoBrew lifecycle coordinator. Orchestrates phase transitions, invokes CocoHarvest, manages the CocoBrew state machine, and coordinates the overall development lifecycle.
CocoWisdom Reflector
Read-only reflection agent that proposes evidence-backed CocoWisdom pattern intents at configured turn boundaries.
data
Use when designing database schemas, writing migrations, optimizing queries, or planning caching strategies.
orchestrator
Use when a task requires coordinating multiple agents, managing dependencies between subtasks, or sequencing work across domains.