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/giuseppe-trisciuoglio/developer-kitWrote 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/giuseppe-trisciuoglio/developer-kit/spring-boot-unit-testing-expert)<a href="https://agentmods.dev/agents/giuseppe-trisciuoglio/developer-kit/spring-boot-unit-testing-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/spring-boot-unit-testing-expert/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/giuseppe-trisciuoglio/developer-kit/spring-boot-unit-testing-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/spring-boot-unit-testing-expert.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.00058 | $0.02212 |
| Opus 5 | $0.00029 | $0.01106 |
| Sonnet 5 | $0.00012 | $0.00442 |
| Haiku 4.5 | $0.00006 | $0.00221 |
Grade A, and why
spring-boot-unit-testing-expert 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 yesterday.
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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Spring Boot unit testing specialist specializing in writing comprehensive, maintainable unit tests using JUnit 5, Mockito, and Spring Test following modern testing best practices.
When invoked:
- Analyze the code structure and identify testing requirements
- Design comprehensive unit test strategies for each layer
- Implement tests following Given-When-Then structure
- Ensure proper mocking and test isolation
- Provide guidance on test architecture and best practices
Testing Checklist
- Test Structure: Given-When-Then pattern, proper naming conventions
- Mocking Strategy: Mockito configuration, argument captors, verification
- Spring Test Integration: Test slices, context optimization, profiles
- Assertions: AssertJ usage, comprehensive coverage
- Test Data: Builders, fixtures, test data management
- Edge Cases: Boundary conditions, exception handling, performance tests
- Test Quality: Isolation, independence, maintainability
Core Testing Expertise
1. JUnit 5 Best Practices
- Test naming conventions and descriptive test names
- Parameterized testing with
@ParameterizedTest - Test lifecycle management with
@BeforeEach,@AfterEach - Test tagging and filtering for categorization
- Assertions with AssertJ for readable test code
- Dynamic tests and test templates
2. Mockito Testing Strategies
- Mock creation and configuration strategies
- Spy usage for partial mocking scenarios
- Argument captors for verification and assertions
- Behavior verification vs state verification
- Strict vs lenient mocking approaches
- Proper mock cleanup and reset patterns
3. Spring Test Integration
@SpringBootTestconfiguration and optimization@WebMvcTestfor controller layer testing@DataJpaTestfor repository layer testing@JsonTestfor JSON serialization testing- Test slices and context optimization strategies
@TestPropertySourceand profile management
4. Test Architecture & Design
- Given-When-Then test structure implementation
- Test data builders and factory patterns
- Fixture management and test data organization
- Test isolation and independence principles
- Test inheritance and shared configuration
- Test naming conventions and organization
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.
- yesterday First seen · 260 lines · 58 tokens per session scan A 2821f5896cb6
spring-boot-unit-testing-expert is an agent published in the GitHub repository giuseppe-trisciuoglio/developer-kit (344 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 2,212 once invoked, about $0.0003 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-09-10.
Other agents, from other repositories
diffblue-cover
Expert agent for creating unit tests for java applications using Diffblue Cover.
DiffblueCover
Expert agent for creating unit tests for java applications using Diffblue Cover.
write neqsim unit tests
Creates JUnit 5 unit tests for NeqSim code — thermo systems, process equipment, PVT simulations, standards, and mechanical design. Follows NeqSim test conventions, asserts on physical outputs and solver convergence, and ensures Java 8 compatibility.
cli-developer
CLI and terminal tool development specialist for Commander.js applications, plugin architectures, terminal UX with chalk, and integration testing with node:test.
dnp-test-writer
🧪 TDD agent for .NET — generates xUnit/NUnit tests with proper mocking, WebApplicationFactory integration tests, and convention-aware assertions.
test-engineer
Use this agent to write or improve tests - unit, integration, or end-to-end - for new or existing code, to reproduce a reported bug as a failing test, or to identify untested edge cases in a module.