521-frameworks-micronaut-testing-unit-tests

521-frameworks-micronaut-testing-unit-tests is a skill for Claude Code, Codex from jabrena/plinth. It costs 150 tokens per session (704 once invoked), scanned A, original, Apache-2.0.

A guide for writing unit tests in Micronaut Java applications, using JUnit 5 and Mockito, with focused options for dependency injection and HTTP checks.

In plain words
What is it for?
Use it to add or improve unit tests for services, configuration, repositories, and HTTP endpoints in a Micronaut project.
Why use it?
It helps you choose between fast isolated tests and Micronaut tests that load application wiring, while keeping configuration and Maven test naming predictable.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to add or improve unit tests for services, configuration, repositories, and HTTP endpoints in a Micronaut project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jabrena/plinth/521-frameworks-micronaut-testing-unit-tests
Install

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.

Any agent
npx skills add jabrena/plinth --skill 521-frameworks-micronaut-testing-unit-tests
Clone the repo
git clone --depth 1 https://github.com/jabrena/plinth

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin 521-frameworks-micronaut-testing-unit-tests/plugin install 521-frameworks-micronaut-testing-unit-tests after adding the marketplace above.

Wrote 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.

agentmods badge for 521-frameworks-micronaut-testing-unit-tests

README.md
[![agentmods](https://agentmods.dev/badge/skills/jabrena/plinth/521-frameworks-micronaut-testing-unit-tests/github.svg)](https://agentmods.dev/skills/jabrena/plinth/521-frameworks-micronaut-testing-unit-tests)
Your own site
<a href="https://agentmods.dev/skills/jabrena/plinth/521-frameworks-micronaut-testing-unit-tests"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/521-frameworks-micronaut-testing-unit-tests/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.

agentmods 80×15 button for 521-frameworks-micronaut-testing-unit-tests

Your own site · 80×15
<a href="https://agentmods.dev/skills/jabrena/plinth/521-frameworks-micronaut-testing-unit-tests"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/521-frameworks-micronaut-testing-unit-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 150 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 704 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00150 $0.00704
Opus 5 $0.00075 $0.00352
Sonnet 5 $0.00030 $0.00141
Haiku 4.5 $0.00015 $0.00070

Measured 6d ago against content hash 1eb9606316ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

521-frameworks-micronaut-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 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.

skills/521-frameworks-micronaut-testing-unit-tests/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Micronaut Unit Testing

Apply fast testing strategies for Micronaut: Mockito-first, narrow @MicronautTest when HTTP or DI replacement is required.

What is covered in this Skill?

  • Pure JUnit 5 + Mockito without container boot
  • @MicronautTest with @MockBean factory methods for collaborators
  • HttpClient blocking exchanges against the embedded server
  • @Property for deterministic configuration in tests
  • @ParameterizedTest with @CsvSource / @MethodSource
  • Naming: *Test → Surefire; *IT → Failsafe when configured
  • When to escalate to @522

Scope: Apply recommendations based on the reference rules and good/bad code examples.

Constraints

Compile before test refactors; verify the full suite after.

  • MANDATORY: Run ./mvnw compile or mvn compile before applying any change
  • SAFETY: If compilation fails, stop immediately
  • VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
  • BEFORE APPLYING: Read the reference for detailed rules and examples
  • EDGE CASE: If request scope is ambiguous, stop and ask a clarifying question before applying changes
  • EDGE CASE: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance

When to use this skill

  • Add or improve unit tests in a Micronaut project
  • Reduce unnecessary @MicronautTest usage with Mockito-first tests
  • Write Mockito-first unit tests for Micronaut services
  • Mock Micronaut bean collaborators in unit tests
  • Review fast Micronaut tests without application context

Workflow

  1. Read reference and assess project context

Read references/521-frameworks-micronaut-testing-unit-tests.md and inspect the current project setup before proposing changes.

  1. Gather scope and decide target improvements

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

  1. Apply framework-aligned changes

Implement or refactor configuration/code following the reference patterns and project conventions.

Read the full file on GitHub · 65 lines

Files

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.

Changes

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.

  1. 6d ago First seen · 65 lines · 150 tokens per session scan A 1eb9606316ba

Subscribe to this mod's changes

521-frameworks-micronaut-testing-unit-tests is a skill published in the GitHub repository jabrena/plinth (437 stars, last pushed yesterday), licensed Apache-2.0. It adds 150 tokens to every session and 704 once invoked, about $0.0007 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.

Related

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.

decebals/claude-code-java · 45 tokens

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…

ArabelaTso/Skills-4-SE · 111 tokens

incremental-java-programmer

Incrementally implement new features in Java repositories from natural language descriptions. Use when adding functionality to existing Java codebases (Maven or Gradle projects). Takes a feature description as input and outputs modified repository with implementation code, corresponding JUnit tests, and verification…

ArabelaTso/Skills-4-SE · 78 tokens

craft-pest

Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…

michtio/craftcms-claude-skills · 353 tokens

java-unit-test-generator

Generates JUnit unit tests for Java classes with loop prevention and incremental generation. Triggers on: "generate unit tests", "create JUnit tests", "test Java class", "add test coverage".

timwukp/agent-skills-best-practice · 46 tokens

test-go

Write, review, and improve Go test code for this project. Use whenever generating, reviewing, or modifying Go tests - including when invoked by the Tester agent, the /test prompt, or any test-related request. Covers table-driven tests, subtests, t.Parallel(), test helpers with t.Helper(), error assertions via…

sergeyklay/.agents · 109 tokens