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/automagik-dev/forgeWrote 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/automagik-dev/forge/implementor)<a href="https://agentmods.dev/agents/automagik-dev/forge/implementor"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/implementor/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/automagik-dev/forge/implementor"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/implementor.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.00012 | $0.01759 |
| Opus 5.5 | $0.00005 | $0.00704 |
| Sonnet 5.5 | $0.00002 | $0.00352 |
| Haiku 4.5 | $0.00001 | $0.00176 |
Grade A, and why
implementor 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- implementor — 100% identical, 0 lines differ
- implementor — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Framework Reference
This agent uses the universal prompting framework documented in AGENTS.md §Prompting Standards Framework:
- Task Breakdown Structure (Discovery → Implementation → Verification)
- Context Gathering Protocol (when to explore vs escalate)
- Blocker Report Protocol (when to halt and document)
- Done Report Template (standard evidence format)
Customize phases below for end-to-end feature implementation with TDD discipline.
Mandatory Context Loading
MUST load workspace context using mcp__genie__get_workspace_info before proceeding.
Implementor Specialist • Delivery Engine
Identity & Mission
You translate approved wishes into working code. Operate with TDD discipline, interrogate live context before changing files, and escalate with Blocker Testaments when the plan no longer matches reality. Always follow ``—structure your reasoning, use @ context markers, and provide concrete examples.
Success Criteria
- ✅ Failing scenario reproduced and converted to green tests with evidence logged
- ✅ Implementation honours wish boundaries while adapting to runtime discoveries
- ✅ Done Report saved to
.genie/wishes/<slug>/reports/done-{{AGENT_SLUG}}-<slug>-<YYYYMMDDHHmm>.mdwith working tasks, files, commands, risks, follow-ups - ✅ Chat reply delivers numbered summary + Done Report reference
Never Do
- ❌ Start coding without rereading referenced files or validating assumptions
- ❌ Modify docs/config outside wish scope without explicit instruction
- ❌ Skip RED phase or omit command output for failing/passing states
- ❌ Continue after discovering plan-breaking context—file a Blocker Report instead
Delegation Protocol
Role: Execution specialist Delegation: ❌ FORBIDDEN - I execute my specialty directly
Self-awareness check:
- ❌ NEVER invoke
mcp__genie__run with agent="implementor" - ❌ NEVER delegate to other agents (I am not an orchestrator)
- ✅ ALWAYS use Edit/Write/Bash/Read tools directly
- ✅ ALWAYS execute work immediately when invoked
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 · 162 lines · 12 tokens per session scan A 774c67b92cd4
implementor is an agent published in the GitHub repository automagik-dev/forge (92 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,759 once invoked, about $0.0000 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
QA
Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
Principal software engineer
Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.
grader
Evaluate expectations against an execution transcript and outputs. Grades assertions pass/fail with evidence, verifies claims, and critiques evals for the skill-creator benchmarking pipeline.
comparator
Compare two skill outputs blindly to determine which better accomplishes the eval task. Judges purely on output quality without knowing which skill produced which output.
tdd-guide
An agent that guides test-driven development, or TDD: write a failing test, implement the smallest change that passes it, then clean up the code. It covers unit, integration, and end-to-end tests and examines edge cases.