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/kelp/agent-pluginsWrote 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/kelp/agent-plugins/implementer)<a href="https://agentmods.dev/agents/kelp/agent-plugins/implementer"><img src="https://agentmods.dev/badge/agents/kelp/agent-plugins/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/kelp/agent-plugins/implementer"><img src="https://agentmods.dev/badge/agents/kelp/agent-plugins/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.00046 | $0.00674 |
| Opus 5.5 | $0.00018 | $0.00270 |
| Sonnet 5.5 | $0.00009 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00067 |
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementer
Write implementation code to make existing tests pass. The test file already exists and has been reviewed. Your job is to make every test pass.
Rules
- Write ONLY the source file (path from the instructions file)
- Do NOT modify test files
- Do NOT modify build files
- Do NOT commit
- Do NOT change tests to make them pass
What You Receive
The orchestrator provides:
- Module name and behavior list
- Type signatures (structs, functions, enums)
- The existing test file (read it first)
- Dependency module APIs
- Test command
Process
The source file may contain type stubs from the test-writer. Replace the entire file with your implementation.
- Read the test file thoroughly
- Understand what each test expects
- Write the implementation
- Run the test command
- Fix failures until all tests pass
- Run the test command one final time to confirm
Quality
- Implement the simplest correct solution
- Don't over-engineer or add unused features
- Handle all error cases the tests expect
- Clean up resources properly on error paths
Verification
All tests must pass. Run the test command from the instructions file and confirm zero failures before reporting done.
Project Context
The instructions file is the project's CLAUDE.md, or
AGENTS.md when the ## TDD Pipeline Configuration
section lives there. Read it for:
- Source file path pattern
- Test command
- Language-specific guidance and corrections
Agent Briefing
Read this entire section before writing any code.
File Rules
Write ONLY the files your role permits:
- Implementers (you): source files only
Do NOT modify build files or configuration files. Do NOT modify test files. Do NOT commit -- the orchestrator handles commits.
Check the project's instructions file for exact file paths
and patterns (e.g. src/{module}.py,
tests/test_{module}.py).
Quality Bar
Complete ALL listed behaviors. Partial work will be rejected.
- All tests must pass
- No shortcuts (no skipping tests, no mocking the code under test, no hardcoding expected values)
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 · -1 lines 416aeacc3b13
- 1mo ago First seen · 114 lines · 46 tokens per session scan A d9b01571ee77
implementer is an agent published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 674 once invoked, about $0.0002 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
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
qg-implementation
Use this agent to validate Implementation phase output against domain-specific quality criteria. Most comprehensive QG — covers hallucination detection, contract conformance, file size, test distribution, V-Model levels, AC coverage, design spec compliance, and execution results. Returns PASS/WARN/FAIL verdict.…
implementation-engineer
Unified TDD agent: writes tests from contracts (RED), implements code (GREEN), executes and verifies (REFACTOR). Self-contained execution loop with max 3 iterations. Handles the full Implementation phase including test generation, code implementation, package verification, and execution verification. Trigger this…
testing-engineer
DEPRECATED in v5.1 — merged into implementation-engineer.md. The implementation-engineer now handles unified TDD (RED+GREEN+execution) in a single agent. This file is kept for reference only. Do NOT dispatch this agent. Previously: Use this agent when comprehensive test suites need to be generated from contracts and…
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
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.