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 niels-emmer/myace --skill test-pyramid-springgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/test-pyramid-spring)<a href="https://agentmods.dev/skills/niels-emmer/myace/test-pyramid-spring"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/test-pyramid-spring/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/skills/niels-emmer/myace/test-pyramid-spring"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/test-pyramid-spring.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.00021 | $0.00295 |
| Opus 5 | $0.00010 | $0.00148 |
| Sonnet 5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
Spring Test Pyramid 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 6d 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
Purpose
Test Spring Boot applications at the right level — fast unit tests for logic, slower integration tests for data access.
Checklist
- Unit tests (JUnit + Mockito): test service-layer logic in isolation. Mock repository and external dependencies. Fast — run in milliseconds.
- Repository integration tests (
@DataJpaTest): test custom queries, entity mappings, and constraint enforcement against a real or embedded database. - Controller slice tests (
@WebMvcTest): test request mapping, validation, and response serialization. Mock service layer. - Full context tests (
@SpringBootTest): use sparingly for critical end-to-end paths only. Slow — don't use for every test. - Coverage: every service method has a unit test. Every custom repository query has an integration test. Every controller endpoint has a slice test for error paths.
Expected output
A test suite where unit tests cover business logic, integration tests cover data access, and full-context tests cover only critical paths.
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.
- 6d ago First seen · 24 lines · 21 tokens per session scan A dcf9e96e409a
Spring Test Pyramid is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 295 once invoked, about $0.0001 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-03.
Other skills, from other repositories
loom-test-strategy
Test strategy guidance covering pyramid design, coverage, test categorization, flaky tests, infrastructure, and risk-based prioritization.
loom-testing
Test implementation across unit, integration, e2e, security, infrastructure, data pipeline, and ML domains.
continuous-testing
Continuous test-driven development loop — after every code change, builds the project, starts the server, and runs Unit Tests, Integration Tests, and System Tests. Applies on top of microprofile-server skill. Use during development when you want full verification after each change. Triggers on "continuous testing"…
nestjs-testing-expert
NestJS testing mechanics with Jest — building testing modules, mocking providers and repositories, writing service and controller specs, and driving HTTP end-to-end tests through the real application. Use for any test touching a NestJS service, controller, guard, module, or API endpoint, including test-module setup…
nestjs-testing
NestJS unit and E2E testing — Test.createTestingModule(), mocking providers with jest, supertest for HTTP assertions. Use when writing tests for NestJS services, controllers, or full application flows. Apply whenever user instantiates NestJS services with new ServiceName() instead of Test.createTestingModule(), uses a…
testing-setup
Analyze and create a testing strategy for native Android apps - install testing libraries, set up test infrastructure, create harnesses for unit tests, UI tests, screenshot tests, and end-to-end tests.