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/loiane/specs-driven-development-spring-angular/junit5-testcontainers-patternsnpx skills add loiane/specs-driven-development-spring-angular --skill junit5-testcontainers-patternsgit clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angularWhat 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.00050 | $0.01343 |
| Opus 5 | $0.00025 | $0.00672 |
| Sonnet 5 | $0.00010 | $0.00269 |
| Haiku 4.5 | $0.00005 | $0.00134 |
Grade A, and why
junit5-testcontainers-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JUnit 5 + Testcontainers patterns
Choose the smallest scope that covers the AC
| AC type | Use |
|---|---|
| Pure logic (calculator, validator, mapper) | Plain JUnit 5, no Spring |
| Controller validation, status codes, JSON shape | @WebMvcTest |
| JPA query / mapping | @DataJpaTest + Testcontainers (@ServiceConnection) |
| End-to-end through HTTP, with DB / external | @SpringBootTest(webEnvironment = RANDOM_PORT) + Testcontainers |
| Cache, security filter chain, bean wiring | targeted slice (e.g. @WebMvcTest + @Import) |
@SpringBootTest is a last resort. If a slice test can cover it, use the slice.
Naming + traceability
-
Every
@Testand@ParameterizedTestmethod MUST carry@DisplayName. No exceptions — write the display name before the test body so articulating it forces clarity about what the test verifies. (Project rule:feedback_displayname_on_every_test.md.) -
The full annotation block on every test method is all three lines, in this order:
@Test @Tag("AC-007") @DisplayName("AC-007: given expired gift card, when applied, then returns 4xx") void appliesExpiredGiftCard() { ... } -
Display-name format for AC-traced tests:
"<T-ID>: given <precondition>, when <action>, then <outcome>". Short BDD-style sentence is acceptable for utility/regression tests not tied to a specific AC. -
@Tag("AC-NNN")makes the test machine-readable for the traceability matrix. -
One AC per test method when feasible.
-
The simplify phase audits every newly-authored or modified test in the diff for
@DisplayName— that's the safety net if the red phase missed it.
Testcontainers with @ServiceConnection (Spring Boot 4)
@DataJpaTest
@Testcontainers
class GiftCardRepositoryTest {
@Container @ServiceConnection
static PostgreSQLContainer<?> postgres = new PostgreSQLContainer<>("postgres:17-alpine");
@Autowired GiftCardRepository repo;
@Test
@DisplayName("AC-004: given a new gift card, when saved and reloaded, then balance is preserved")
@Tag("AC-004")
void persistsBalance() {
var saved = repo.save(GiftCard.with(BigDecimal.valueOf(100)));
assertThat(repo.findById(saved.id()).orElseThrow().balance())
.isEqualByComparingTo("100");
}
}
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.
- 2d ago First seen · 131 lines · 50 tokens per session scan A 882073908baf
junit5-testcontainers-patterns is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 1,343 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-30.
Other skills, from other repositories
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
spec-kitty-implement-review
Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop"…
spec-kitty-mission-review
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review"…
spec-kitty-program-orchestrate
Orchestrate a multi-repo, multi-mission Spec Kitty program end-to-end: run specify → plan → tasks → implement → review → merge → mission-review → post-merge fixes across several repositories in a defined dependency order, using background sub-agents for parallel work and a pulse-heartbeat safety net for long…
spec-kitty-runtime-next
Drive the canonical spec-kitty next --mission control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the…
spec-kitty-bulk-edit-classification
Recognize when a mission is a bulk edit and drive the occurrence-classification guardrail on the user's behalf. Triggers: user says any variant of "rename X to Y", "change the terminology", "migrate all occurrences", "replace across the codebase", "the X feature is now the Y feature", "sed everywhere", or any request…