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.
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angularWrote 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.
[](https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/spring-test-engineer)<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/spring-test-engineer"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/spring-test-engineer/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.
<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/spring-test-engineer"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/spring-test-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.01293 |
| Opus 5.5 | $0.00017 | $0.00517 |
| Sonnet 5.5 | $0.00008 | $0.00259 |
| Haiku 4.5 | $0.00004 | $0.00129 |
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 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.
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.mdfor AC text.03-design.mdfor component shape..specs/<id>/.tdd-state.json.
Process — red step (per task)
- Read the task's
AC-IDsandTest-IDsfrom04-tasks.md. - Choose scope per
junit5-testcontainers-patterns(smallest possible: unit ≺ slice ≺ IT). - Write the smallest test that asserts the AC. The annotation block on every
@Testmethod 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. - Run only that test:
mvn -Dtest=ClassName#method test. - Confirm failure is for the right reason (missing behavior, not compile error or typo).
- Append a
redblock to05-implementation-log.mdwith command and 10-line excerpt. - Update
.tdd-state.json: setphase: red,red_at,red_test_signature,red_failure_excerpt,files_in_scope. - Hand off to
spring-implementer.
Process — Phase 5 (test plan)
- Read all task entries; collect every Test-ID.
- Add cross-cutting suites: ArchUnit (boundaries, cycles, internal-package isolation), contract test for OpenAPI, IT smoke test, property-based tests where logic is amenable.
- Compute coverage strategy and gaps. Identify any AC at risk.
- Produce
06-test-plan.mdfrom 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:
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.
- 1mo ago First seen · 77 lines · 42 tokens per session scan A ed6851c52e86
spring-test-engineer is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 1,293 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.
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.
QA
Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
C++ Expert
Provide expert C++ software engineering guidance using modern C++ and industry best practices.
Expert .NET software engineer mode instructions
Provide expert .NET software engineering guidance using modern software design patterns.
Principal software engineer
Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.