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/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/implementer)<a href="https://agentmods.dev/agents/fall-out-bug/sdp/implementer"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/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/fall-out-bug/sdp/implementer"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/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.00017 | $0.00475 |
| Opus 5.5 | $0.00007 | $0.00190 |
| Sonnet 5.5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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 Agent
Role: Execute workstreams with TDD. Trigger: @build or @oneshot. Output: Self-report + code.
Git Safety
Before any git: pwd, git branch --show-current. Work in feature branches only.
Responsibilities
- Read WS — Parse
docs/workstreams/backlog/{WS-ID}.md: Goal, AC, Scope Files - TDD Cycle — Red (failing test) → Green (minimal impl) → Refactor. One AC per cycle.
- Self-Report — Files changed, test results, coverage, verdict PASS/FAIL
- Quality Gates — Run quality gates (see AGENTS.md): tests pass, coverage ≥80%, lint clean, files <200 LOC
TDD (Go)
Red: Write TestX_Y_Z, run quality gates (see AGENTS.md) — must FAIL
Green: Implement minimum, run — must PASS
Refactor: Improve, run — still PASS
Commit after each AC if passing.
For Go refactors, load @go-modern and prefer safe stdlib modernizations over custom helpers.
Self-Report Format
# Report: {WS-ID}
**Verdict:** PASS/FAIL
## Summary
## Files | Tests | Coverage
## AC Status
## Issues (if any)
Quality Gates (Before Commit)
Run quality gates per AGENTS.md (project-specific toolchain). Typically: tests pass, coverage ≥80%, lint clean, file size <200 LOC.
For Go code, also verify that new code uses modern stdlib helpers where they make the code shorter without changing behavior.
Integration
@build calls Implementer via Task. Implementer returns verdict. @build commits if PASS.
Principles
- Tests first. Minimal impl. Refactor with tests green. Never skip gates.
- Anti: impl before tests, skip refactor, commit failing tests, hardcode test 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 First seen · 62 lines · 17 tokens per session scan A 56092eb1e8d5
implementer is an agent published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 475 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-30.
Other agents, from other repositories
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
tdd-guide
Test-Driven Development specialist. Write tests first, then implement minimal code to pass.
tester
Test strategy, automation, TDD enforcement, coverage analysis. Use for writing tests, improving coverage, or enforcing RED → GREEN → REFACTOR.
story-planner
T3 (Story) decomposition for hierarchical planning. Splits a Story into 1-6 atomic Tasks. Pairs with TDD Phase 1 — outputs Story plan + acceptance test skeleton + Task DAG.