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 jabrena/plinth --skill 501-frameworks-micronaut-coregit clone --depth 1 https://github.com/jabrena/plinthWrote 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/plinth/501-frameworks-micronaut-core)<a href="https://agentmods.dev/skills/jabrena/plinth/501-frameworks-micronaut-core"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/501-frameworks-micronaut-core/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/jabrena/plinth/501-frameworks-micronaut-core"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/501-frameworks-micronaut-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00139 | $0.00738 |
| Opus 5 | $0.00069 | $0.00369 |
| Sonnet 5 | $0.00028 | $0.00148 |
| Haiku 4.5 | $0.00014 | $0.00074 |
Grade A, and why
501-frameworks-micronaut-core 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Micronaut Core Guidelines
Apply Micronaut core guidelines for DI, configuration, HTTP adapters, and operations.
What is covered in this Skill?
- Thin
mainwithMicronaut.run(Application.class, args) - Bean scopes: @Singleton, @Prototype; request scope only when justified
- Constructor injection with
jakarta.inject.Inject - @Factory for third-party or explicit bean construction
- @ConfigurationProperties (grouped settings) vs scattered @Property
- @Requires and environments instead of env branching in domain code
- Thin @Controller types delegating to @Singleton services
- @Scheduled with explicit failure visibility
- @ExecuteOn(TaskExecutors.BLOCKING) (or virtual-thread executors) for blocking I/O off the event loop
- Netty graceful shutdown properties
- AOP interceptors for cross-cutting concerns
Scope: Apply recommendations based on the reference rules and good/bad code examples.
Constraints
Before applying Micronaut changes, ensure the project compiles. If compilation fails, stop immediately. After applying improvements, run full verification.
- MANDATORY: Run
./mvnw compileormvn compilebefore applying any change - PREREQUISITE: Project must compile successfully before applying Micronaut core improvements
- SAFETY: If compilation fails, stop immediately — compilation failure is a blocking condition
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter applying improvements - BEFORE APPLYING: Read the reference for detailed rules, good/bad patterns, and constraints
When to use this skill
- Review Java code for Micronaut application structure and beans
- Apply best practices for Micronaut configuration, @Requires, and factories
- Improve scheduling, shutdown, or threading in Micronaut services
- Review Micronaut dependency injection scopes and factories
- Configure Micronaut @Requires conditions for environments
Workflow
- Read reference and assess project context
Read references/501-frameworks-micronaut-core.md and inspect the current project setup before proposing changes.
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.
- 6d ago First seen · 68 lines · 139 tokens per session scan A 1a32b39e9978
501-frameworks-micronaut-core is a skill published in the GitHub repository jabrena/plinth (438 stars, last pushed today), licensed Apache-2.0. It adds 139 tokens to every session and 738 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.
Other skills, from other repositories
spring-boot-engineer
Generates Spring Boot 3.x configurations, creates REST controllers, implements Spring Security 6 authentication flows, sets up Spring Data JPA repositories, and configures reactive WebFlux endpoints. Use when building Spring Boot 3.x applications, microservices, or reactive Java applications; invoke for Spring Data…
spring-boot-patterns
Spring Boot best practices and patterns. Use when creating controllers, services or repositories, or when the user asks about Spring Boot layering, wiring, configuration or exception handling. For JPA and Hibernate behaviour, use jpa-patterns instead.
api-contract-review
Review REST API contracts for HTTP semantics, versioning, backward compatibility, and response consistency. Use when user asks "review API", "check endpoints", "REST review", or before releasing API changes.
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.