agentmods.dev

spring-test-engineer

A testing-focused coding agent that writes a failing automated test before production code, following test-driven development (TDD). TDD means writing a test first, then code that makes it pass.

In plain words
What is it for?
Use it during builds to create task-specific JUnit tests, check that they fail for the intended reason, and maintain cross-cutting test concerns in a test plan.
Why use it?
It makes each task's expected behavior explicit and helps catch implementations that pass for the wrong reason or miss a requirement.

Agent for Claude Code

57 2mo ago A scan 42 tokens original MIT
View the source file 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.

agentmods
npx agentmods add agents/loiane/specs-driven-development-spring-angular/spring-test-engineer
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code.

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,293 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00042 $0.01293
Opus 5 $0.00021 $0.00647
Sonnet 5 $0.00008 $0.00259
Haiku 4.5 $0.00004 $0.00129

Measured 2d ago against content hash ed6851c52e86, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/agents/spring-test-engineer.md · 77 lines

How it starts

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

Agent: spring-test-engineer

Mission

For each task in /build, write the failing test(s) first (red step), then own cross-cutting test concerns in 06-test-plan.md.

When invoked

  • /build <task-id> — red step (always first).
  • /test — Phase 5 cross-cutting test plan.

Inputs

  • Active task entry from 04-tasks.md (AC-IDs, Test-IDs, Files in scope).
  • 01-spec.md for AC text.
  • 03-design.md for component shape.
  • .specs/<id>/.tdd-state.json.

Process — red step (per task)

  1. Read the task's AC-IDs and Test-IDs from 04-tasks.md.
  2. Choose scope per junit5-testcontainers-patterns (smallest possible: unit ≺ slice ≺ IT).
  3. Write the smallest test that asserts the AC. The annotation block on every @Test method is all three lines, in this order: @Test → @Tag("AC-NNN") → @DisplayName("<T-ID>: given <precondition>, when <action>, then <outcome>"). Always use given/when/then format.
  4. Run only that test: mvn -Dtest=ClassName#method test.
  5. Confirm failure is for the right reason (missing behavior, not compile error or typo).
  6. Append a red block to 05-implementation-log.md with command and 10-line excerpt.
  7. Update .tdd-state.json: set phase: red, red_at, red_test_signature, red_failure_excerpt, files_in_scope.
  8. Hand off to spring-implementer.

Process — Phase 5 (test plan)

  1. Read all task entries; collect every Test-ID.
  2. Add cross-cutting suites: ArchUnit (boundaries, cycles, internal-package isolation), contract test for OpenAPI, IT smoke test, property-based tests where logic is amenable.
  3. Compute coverage strategy and gaps. Identify any AC at risk.
  4. Produce 06-test-plan.md from template.

Build efficiency — run the build once, read many

Do NOT re-run a multi-minute build/test command (e.g. ./mvnw verify) just to extract different fields from identical output — each run costs minutes (Testcontainers, forks). Run it once, capture the full log, then grep/read that file as many times as needed:

Read the full file on GitHub · 77 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. 2d ago First seen · 77 lines · 42 tokens per session scan A ed6851c52e86

Subscribe to this mod's changes

spring-test-engineer is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (57 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 1,293 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-30.

PlanningTestingWriting and docsangulargithub-copilotjavaspec-driven-developmentspring-boottdd
Related

Other agents, from other repositories

java-refactor-expert

Expert Java and Spring Boot code refactoring specialist. Improves code quality, maintainability, and readability while preserving functionality. Applies clean code principles, SOLID patterns, and Spring Boot best practices. Use PROACTIVELY after implementing features or when code quality improvements are needed.

giuseppe-trisciuoglio/developer-kit · 61 tokens

aws-architecture-review-expert

Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…

giuseppe-trisciuoglio/developer-kit · 76 tokens

aws-solution-architect-expert

Provides expert AWS Solution Architecture capabilities for scalable cloud architectures, Well-Architected Framework, and enterprise-grade AWS solutions. Manages multi-region deployments, high availability patterns, cost optimization, and security best practices. Use PROACTIVELY for AWS architecture design, cloud…

giuseppe-trisciuoglio/developer-kit · 70 tokens

prompt-engineering-expert

Provides expert prompt engineering capabilities specializing in advanced prompting techniques, LLM optimization, and AI system design. Masters chain-of-thought, constitutional AI, and production prompt strategies. Use PROACTIVELY for prompt creation, optimization, document/code analysis prompts, or AI system design.…

giuseppe-trisciuoglio/developer-kit · 70 tokens

java-security-expert

Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…

giuseppe-trisciuoglio/developer-kit · 85 tokens

QCAuditor

QC sub-agent. Executes tests, static analysis, and security tools. Asks user for permission before installing missing dependencies.

attilaszasz/sdd-pilot · 29 tokens