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 skills/jabrena/cursor-rules-examples/321-frameworks-spring-boot-testing-unit-testsnpx skills add jabrena/cursor-rules-examples --skill 321-frameworks-spring-boot-testing-unit-testsgit clone --depth 1 https://github.com/jabrena/cursor-rules-examplesWrote 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/skills/jabrena/cursor-rules-examples/321-frameworks-spring-boot-testing-unit-tests)<a href="https://agentmods.dev/skills/jabrena/cursor-rules-examples/321-frameworks-spring-boot-testing-unit-tests"><img src="https://agentmods.dev/badge/skills/jabrena/cursor-rules-examples/321-frameworks-spring-boot-testing-unit-tests.svg" alt="Measured on agentmods" 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 | $0.00084 | $0.00432 |
| Opus 5 | $0.00042 | $0.00216 |
| Sonnet 5 | $0.00017 | $0.00086 |
| Haiku 4.5 | $0.00008 | $0.00043 |
Grade A, and why
321-frameworks-spring-boot-testing-unit-tests 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 4d 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.
What it actually says
Spring Boot Unit Testing with Mockito
Apply Spring Boot unit testing guidelines with Mockito.
What is covered in this Skill?
- Pure unit tests: @ExtendWith(MockitoExtension.class), @Mock, @InjectMocks for @Service/@Component (no Spring context)
- Slice tests: @WebMvcTest, @MockBean for controllers
- @JsonTest for JSON serialization
- @TestConfiguration, @ActiveProfiles for test setup
Scope: Apply recommendations based on the reference rules and good/bad code examples. For integration tests use @322-frameworks-spring-boot-testing-integration-tests.
Constraints
Before applying any test changes, ensure the project compiles. If compilation fails, stop immediately. After applying improvements, run full verification.
- MANDATORY: Run
./mvnw compileormvn compilebefore applying any change - SAFETY: If compilation fails, stop immediately
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter applying improvements - BEFORE APPLYING: Read the reference for detailed rules and good/bad patterns
When to use this skill
- Review Java code for Spring Boot unit tests
- Apply best practices for Spring Boot unit tests in Java code
Reference
For detailed guidance, examples, and constraints, see references/321-frameworks-spring-boot-testing-unit-tests.md.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 39 lines · 84 tokens per session scan A 2dcfa4bb28ec
321-frameworks-spring-boot-testing-unit-tests is a skill published in the GitHub repository jabrena/cursor-rules-examples (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 84 tokens to every session and 432 once invoked, about $0.0004 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 skills, from other repositories
pytest-expert
Pytest fixtures, parametrize, mock/monkeypatch, async testing with pytest-asyncio, and coverage reporting.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
Karma Testing
Comprehensive Karma test runner skill for browser-based JavaScript unit testing with Jasmine, Mocha, or QUnit frameworks, real browser execution, coverage reporting, and CI/CD pipeline integration.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
component-creation
Step-by-step workflow for creating accessible, tested UI components. Use when the user asks to create a new UI component.
awesome-test-writing
Designs and writes tests that catch real regressions — placement (unit/integration/E2E), factories and fixtures, behavior-first assertions, characterization tests for legacy code, property/fuzz tests for parsers. Use when asked to 'write tests', 'add test coverage', 'test this module', 'напиши тесты', when a bug fix…