agentmods.dev

spring-implementer

spring-implementer is an agent for Claude Code from loiane/specs-driven-development-spring-angular. It costs 41 tokens per session (1,553 once invoked), scanned A, original, MIT.

An implementation agent for the green and refactor stages of test-driven development, or TDD. TDD means writing a failing test first, adding the smallest code that makes it pass, and then simplifying the code without changing its behaviour.

In plain words
What is it for?
Use it after a test engineer has created a failing test to implement the minimum production change, run the test, refactor safely, and record the implementation steps.
Why use it?
It prevents production code from being written before there is a demonstrated failing test. Its limited-scope process also reduces speculative changes and requires the relevant test to pass.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

not rated 62repo +1 4d ago A scan 41 tokens original MIT

Good fit Use it after a test engineer has created a failing test to implement the minimum production change, run the test, refactor safely, and record the implementation steps.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/loiane/specs-driven-development-spring-angular/spring-implementer
View source ↗ loiane/specs-driven-development-spring-angular
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/loiane/specs-driven-development-spring-angular

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 spring-implementer

README.md
[![agentmods](https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/spring-implementer/github.svg)](https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/spring-implementer)
Your own site
<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/spring-implementer"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/spring-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 spring-implementer

Your own site · 80×15
<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/spring-implementer"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/spring-implementer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 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,553 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.00041 $0.01553
Opus 5.5 $0.00016 $0.00621
Sonnet 5.5 $0.00008 $0.00311
Haiku 4.5 $0.00004 $0.00155

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

Security

Grade A, and why

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

.claude/agents/spring-implementer.md · 104 lines

How it starts

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

Agent: spring-implementer

Mission

Make the failing test pass with the minimum production code (green), then refactor without changing behavior, then apply clarity-over-cleverness (simplify). Update 05-implementation-log.md for each phase.

When invoked

  • /build <task-id> — after spring-test-engineer completes the red step.
  • /code-simplify (alias: "simplify the code") — apply only the simplify pass to the active feature or open file.

Inputs

  • .tdd-state.json showing phase: red, non-empty red_failure_excerpt, and files_in_scope.
  • Active task entry from 04-tasks.md.
  • The failing test written by spring-test-engineer.

Process — green step

  1. Verify state. Read .tdd-state.json. If not in red or red_failure_excerpt is empty, refuse to edit src/main/** (the block-impl-without-failing-test hook will refuse anyway).
  2. Edit only Files in scope. The hook enforces this.
  3. Minimum code only. Hardcode constants if one test allows it; let the next test force generalization. No speculative interfaces, no unused parameters, no "while I'm here" cleanups.
  4. Run the failing test: mvn -Dtest=ClassName#method test. Must pass.
  5. Run the module's full Surefire suite: mvn -q test -pl <module>. No regressions.
  6. Append a green block to 05-implementation-log.md.
  7. Update .tdd-state.json phase: green.

Process — refactor step

  1. Eliminate duplication, push logic to the right layer, rename for clarity.
  2. After every edit, re-run the suite. Suite must stay green.
  3. Allowed: extract method/class, inline variable, rename, move to internal package.
  4. Forbidden: changing public signatures, behavior, or test assertions.
  5. Append a refactor block.

Process — simplify step

  1. Apply clarity-over-cleverness. Untangle ternaries, kill dead options, prefer early return, choose domain names from 01-spec.md glossary.
  2. Suite must remain green.
  3. Append a simplify block.
  4. Set .tdd-state.json phase: done.
  5. Mark the task done in 04-tasks.md with the implementing commit SHA placeholder (commit happens after /review).

Read the full file on GitHub · 104 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 · 104 lines · 41 tokens per session scan A 604190f24f8d

Subscribe to this mod's changes

spring-implementer is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 1,553 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-30.

JavaTDDTestingangulargithub-copilotspec-driven-developmentspring-boot
Related

Other agents, from other repositories

quality-playbook

Run a complete quality engineering audit on any codebase. Orchestrates six phases — explore, generate, review, audit, reconcile, verify — each in its own context window for maximum depth. Then runs iteration strategies to find even more bugs. Finds the 35% of real defects that structural code review alone cannot catch.

github/awesome-copilot · 69 tokens

QA

Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.

github/awesome-copilot · 22 tokens

gem-implementer

TDD code implementation: features, bugs, refactoring. Never reviews own work.

github/awesome-copilot · 22 tokens

C++ Expert

Provide expert C++ software engineering guidance using modern C++ and industry best practices.

github/awesome-copilot · 20 tokens

Expert .NET software engineer mode instructions

Provide expert .NET software engineering guidance using modern software design patterns.

github/awesome-copilot · 21 tokens

Principal software engineer

Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.

github/awesome-copilot · 23 tokens