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/322-frameworks-spring-boot-testing-integration-testsnpx skills add jabrena/cursor-rules-examples --skill 322-frameworks-spring-boot-testing-integration-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/322-frameworks-spring-boot-testing-integration-tests)<a href="https://agentmods.dev/skills/jabrena/cursor-rules-examples/322-frameworks-spring-boot-testing-integration-tests"><img src="https://agentmods.dev/badge/skills/jabrena/cursor-rules-examples/322-frameworks-spring-boot-testing-integration-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.1 | $0.00051 | $0.00354 |
| Opus 5 | $0.00026 | $0.00177 |
| Sonnet 5 | $0.00010 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
322-frameworks-spring-boot-testing-integration-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 5d 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
Java Integration Testing Guidelines
Apply Java integration testing guidelines.
What is covered in this Skill?
- Integration test scope and purpose
- Testcontainers for dependencies
- TestRestTemplate for API testing
- Data management strategies
- Test structure and assertions
- Performance and cleanup
Scope: Apply recommendations based on the reference rules and good/bad code examples.
Constraints
Before applying any integration 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 integration tests
- Apply best practices for Spring Boot integration tests in Java code
Reference
For detailed guidance, examples, and constraints, see references/322-frameworks-spring-boot-testing-integration-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.
- 5d ago First seen · 41 lines · 51 tokens per session scan A e3535831ed9f
322-frameworks-spring-boot-testing-integration-tests is a skill published in the GitHub repository jabrena/cursor-rules-examples (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 51 tokens to every session and 354 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-08-31.
Other skills, from other repositories
testing
TDD, mocks, gauntlet, regression naming. Use when writing or expanding tests, not because testing.mdc is on.
debugging
Evidence-first debug for unknown or intermittent bugs. Use when the cause is unknown or the user asks to diagnose.
redesign-existing-projects
Audit then fix generic or AI-looking sites in place. Product apps apply findings through premium-ui-craft.
now
Write or resume NOW.md. Use when switching chats, pausing a feature, or the user mentions NOW.md, session continuity, or handoff.
debugging-loop
Systematic reproduce-isolate-fix-verify loop for bugs, test failures, and unexpected behavior. Use when something is broken and the cause is not yet known.
tw-component
Generate a UI component using correct Tailwind CSS v4 utility classes, CSS variable theming, and accessibility best practices. Prevents v3 syntax hallucination by grounding output in verified v4 patterns.