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 skills add JeonJe/claude-plugins --skill spring-test-writinggit clone --depth 1 https://github.com/JeonJe/claude-pluginsWrote 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/jeonje/claude-plugins/spring-test-writing)<a href="https://agentmods.dev/skills/jeonje/claude-plugins/spring-test-writing"><img src="https://agentmods.dev/badge/skills/jeonje/claude-plugins/spring-test-writing.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.00085 | $0.01110 |
| Opus 5 | $0.00043 | $0.00555 |
| Sonnet 5 | $0.00017 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
spring-test-writing 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 7d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Test Writing
Test-writing methodology for Java/Spring, distilled from a production multi-module codebase. Entry point: pick the test type, read its reference, and run the quality checklist before commit.
AI 테스트 작성 시 필수 확인
- given/when/then 주석 구조 사용
@DisplayName으로 비즈니스 의도 명시 (팀 언어로)@Nested로 시나리오 그룹화@MockitoBean사용 —@MockBean은 Spring Boot 3.4+에서 레거시Thread.sleep금지 —@Transactional자동 롤백과 관찰 가능한 조건 대기 활용- 테스트 후 반드시 빌드 검증:
./gradlew :{module}:test --tests "ClassName" - 테스트 데이터는 고정 날짜 사용 (
LocalDate.of(...)) —LocalDate.now()금지 - soft-delete 프로젝트라면 프로덕션 코드의 미삭제 조건 누락 여부를 테스트에서 확인
- 커밋 전 references/quality-check.md 실행
테스트 타입 선택
| 타입 | 문서 | 언제 사용 |
|---|---|---|
| 단위 테스트 | references/unit-test.md | Service, Domain 로직 (Spring Context 불필요) |
| 컨트롤러 테스트 | references/controller-test.md | REST API 엔드포인트 + API 문서 자동 생성 |
| DB 통합 테스트 | references/testcontainers-db-test.md | Mapper/Repository 쿼리 검증 — 실 DB 엔진으로 |
| 품질 검증 | references/quality-check.md | 작성 완료 후, 커밋 전 |
모듈별 베이스 클래스 원칙
테스트를 새로 쓰기 전에 그 모듈의 기존 베이스 클래스를 먼저 찾는다 (컨트롤러용 RestDocs 베이스, 통합 테스트 베이스, Testcontainers 베이스). 모듈마다 헬퍼 시그니처·Mock 구성이 다를 수 있으므로, 같은 모듈의 최근 테스트 1개를 열어 패턴을 확인한 뒤 동일하게 작성한다. 베이스 클래스가 없는 모듈에서 처음 만들 때만 인접 모듈 것을 참조해 신설한다.
도메인 테스트 퀵레퍼런스 (복잡 도메인 권장)
핵심 도메인(결제·예약·정산 등)은 테스트 가이드와 별도로 그 도메인 전용 퀵레퍼런스 문서를 유지한다. 새 사람(또는 새 세션의 AI)이 "이 도메인을 건드리면 무엇부터 테스트해야 하나"를 문서 하나로 파악하게 하는 것이 목적. 구성:
- 우선순위 매트릭스 — Critical(배포 전 필수) / High / Medium으로 시나리오를 분류. Critical은 "이게 깨지면 돈/데이터가 틀어지는 것"만.
- 진입점별 테스트 맵 — 커맨드 서비스의 공개 메서드마다 필요한 테스트 케이스 나열.
- 핵심 예외 시나리오 — 이 도메인 특유의 실패 경로 (중복 요청, 한도 초과, 역순 콜백 등).
- DB 검증 체크리스트 — 성공 케이스 후 테이블별 기대 상태 (어느 테이블에 몇 행, 어떤 컬럼 값). "응답 200"이 아니라 영속 상태가 성공의 정의다.
- 부수효과 검증 — 알림·이벤트·캐시 무효화가 발생/미발생해야 하는 조건.
- 패턴 체인 검증 — Factory/Strategy 등 분기 구조가 있으면 각 분기의 선택 조건 테스트.
What ships with it
4 files 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.
- 7d ago First seen · 51 lines · 85 tokens per session scan A 8efb932b5404
spring-test-writing is a skill published in the GitHub repository JeonJe/claude-plugins (3 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 1,110 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
test-quality
Write high-quality JUnit 5 tests with AssertJ assertions. Use when user says "add tests", "write tests", "improve test coverage", or when reviewing/creating test classes for Java code.
java-unit-test
A code-generation guide for Java unit tests in Spring Boot projects. Unit tests check one small piece of code in isolation; Spring Boot is a Java framework for building web applications and services.
typescript
TypeScript strict mode with eslint and jest.
111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a…
java-regression-test-generator
Automatically generate regression tests for Java codebases by analyzing changes between old and new code versions. Use when users need to: (1) Generate tests after refactoring or code changes, (2) Ensure previously tested behavior still works in new versions, (3) Cover modified or newly added code paths, (4) Migrate…
130-java-testing-strategies
Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code…