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.
npx agentmods add agents/fall-out-bug/sdp/implementergit clone --depth 1 https://github.com/fall-out-bug/sdpWhat 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 | $0.00017 | $0.00475 |
| Opus 5 | $0.00009 | $0.00237 |
| Sonnet 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 yesterday.
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.
- yesterday 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 2mo ago), licensed MIT. It adds 17 tokens to every session and 475 once invoked, about $0.0001 per session on Opus 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
Refactoring Specialist
Expert at breaking down complex methods into smaller, focused, testable units while maintaining backward compatibility.
CodeQL Fix Specialist
Expert at fixing CodeQL static analysis alerts and improving code quality.
test-hunter
Generates adversarial tests for a module or feature. Does NOT write happy-path tests — that is the author's job. Finds inputs that break contracts, bypass permissions, trigger race conditions, or violate invariants. Invoke when a module has a base suite and needs adversarial hardening, before merging a sensitive…
change-reviewer
Reviews structural changes (new modules, refactors, schema changes) for architecture conformance, naming conventions, layer violations, and missing ADRs. Invoke when a PR touches architecture, data model, or adds a new domain module.
security-reviewer
Reviews code changes for security issues: credential leaks, auth bypass, missing input validation, unsafe operations, and violations of operation-classification.md. Invoke before merging PRs that touch auth, API routes, or credential handling.
spec-guardian
Verifies the codebase is in sync with the spec (PRD.md, use-cases.md, ADRs, data-model.md). Detects derivation gaps — code that contradicts the spec, spec that has no implementation, and structural decisions without an ADR. Invoke before cutting a release or when drift is suspected.