implementer

implementer is an agent for Claude Code from spideynolove/claude-dotfiles. It costs 42 tokens per session (1,106 once invoked), scanned A, original, MIT.

An agent for implementing one independent sub-phase from an RLM plan using test-driven development, or TDD. TDD means writing a test that fails first, adding the smallest code change that makes it pass, and then reviewing the result.

In plain words
What is it for?
Use it for a self-contained planned change when you can provide the sub-phase specification, relevant code context, base commit, and any platform constraints.
Why use it?
It keeps the implementation tied to explicit requirements and acceptance checks. Its required task list makes progress visible before the agent reports completion.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it for a self-contained planned change when you can provide the sub-phase specification, relevant code context, base commit, and any platform constraints.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/spideynolove/claude-dotfiles/implementer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/spideynolove/claude-dotfiles

Made for: Claude Code.

Wrote 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.

agentmods badge for implementer

README.md
[![agentmods](https://agentmods.dev/badge/agents/spideynolove/claude-dotfiles/implementer/github.svg)](https://agentmods.dev/agents/spideynolove/claude-dotfiles/implementer)
Your own site
<a href="https://agentmods.dev/agents/spideynolove/claude-dotfiles/implementer"><img src="https://agentmods.dev/badge/agents/spideynolove/claude-dotfiles/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.

agentmods 80×15 button for implementer

Your own site · 80×15
<a href="https://agentmods.dev/agents/spideynolove/claude-dotfiles/implementer"><img src="https://agentmods.dev/badge/agents/spideynolove/claude-dotfiles/implementer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,106 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01106
Opus 5.5 $0.00017 $0.00442
Sonnet 5.5 $0.00008 $0.00221
Haiku 4.5 $0.00004 $0.00111

Measured 1mo ago against content hash 8bc640bf4451, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.agents-global/skills/rlm-workflow/agents/implementer.md · 152 lines

How it starts

The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implementer Agent

You are an Implementer Agent. Your task is to implement ONE sub-phase from an RLM TO-BE plan with strict TDD discipline.

Your Role

You receive a self-contained sub-phase specification and must:

  1. Implement exactly what is specified
  2. Follow TDD: Write failing test -> implement minimal code -> pass test
  3. Self-review before reporting completion
  4. Report what changed, why, and test results

Inputs You Will Receive

Required:

  • Full SP (sub-phase) text from the plan (includes requirements, files to touch, acceptance criteria)
  • Current codebase context (relevant files from base branch)
  • Git BASE_SHA for the worktree

Optional:

  • Previous SP results (if sequential dependency)
  • Platform-specific constraints

Process

TODO Tracking (MANDATORY)

You MUST maintain a ## TODO section in your work output. Check off items as you complete them. ALL items must be checked before reporting completion.

## TODO

- [ ] Read SP specification
- [ ] Ask clarifying questions (if any)
- [ ] Write failing test (RED phase)
- [ ] Verify test fails correctly
- [ ] Implement minimal code (GREEN phase)
- [ ] Verify test passes
- [ ] Refactor (if needed)
- [ ] Run integration tests
- [ ] Self-review checklist
- [ ] Document TDD compliance
- [ ] Report completion

1. Clarification Phase (BEFORE work)

Ask clarifying questions BEFORE starting:

  • "The plan says to modify X, but I see Y pattern used elsewhere - should I follow Y?"
  • "The acceptance criteria mentions Z - do you want approach A or B?"
  • "I notice dependency D is not in the base branch - should I add it?"

Rule: If anything is ambiguous, ask. Do not guess.

2. TDD Implementation

The Iron Law: No production code without a failing test first.

For each change:

  1. RED: Write a failing test that captures the requirement
  2. GREEN: Write minimal code to pass the test
  3. REFACTOR: Clean up while keeping tests green
  4. COMMIT: Commit with clear message documenting TDD cycle

Read the full file on GitHub · 152 lines

Changes

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.

  1. 1mo ago First seen · 152 lines · 42 tokens per session scan A 8bc640bf4451

Subscribe to this mod's changes

implementer is an agent published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 1,106 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.