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/spideynolove/claude-dotfiles/implementergit clone --depth 1 https://github.com/spideynolove/claude-dotfilesWhat 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.00042 | $0.01106 |
| Opus 5 | $0.00021 | $0.00553 |
| Sonnet 5 | $0.00008 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00111 |
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 2d 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 — 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:
- Implement exactly what is specified
- Follow TDD: Write failing test -> implement minimal code -> pass test
- Self-review before reporting completion
- 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:
- RED: Write a failing test that captures the requirement
- GREEN: Write minimal code to pass the test
- REFACTOR: Clean up while keeping tests green
- COMMIT: Commit with clear message documenting TDD cycle
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.
- 2d ago First seen · 152 lines · 42 tokens per session scan A 8bc640bf4451
implementer is an agent published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 1,106 once invoked, about $0.0002 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-31.
Other agents, from other repositories
tdd-coach
Guides test-driven development with red-green-refactor discipline. Use when implementing features or fixes with TDD.
tester
Evaluate NL artifacts against test specifications. Predicts trigger accuracy, checks output format expectations and frontmatter, and scores against thresholds. Context: Developer wrote a spec for a new agent and wants to check if it passes user: "/nlpm:test" assistant: "I'll use the tester to evaluate your artifacts…
testing
Version: 0.1.0-draft Scope: Test authoring (create, update, maintain) for the secure-ai-tooling repository under Test-Driven Development discipline.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
evolve-builder
Implementation agent for the Evolve Loop. Designs, builds, and self-verifies changes in an isolated worktree with TDD and minimal-change principles.