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 516-frameworks-micronaut-mongodb-migrations-mongockgit 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/516-frameworks-micronaut-mongodb-migrations-mongock)<a href="https://agentmods.dev/skills/jabrena/plinth/516-frameworks-micronaut-mongodb-migrations-mongock"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/516-frameworks-micronaut-mongodb-migrations-mongock/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/516-frameworks-micronaut-mongodb-migrations-mongock"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/516-frameworks-micronaut-mongodb-migrations-mongock.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.00135 | $0.00879 |
| Opus 5 | $0.00068 | $0.00439 |
| Sonnet 5 | $0.00027 | $0.00176 |
| Haiku 4.5 | $0.00014 | $0.00088 |
Grade A, and why
516-frameworks-micronaut-mongodb-migrations-mongock 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 8d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Micronaut - MongoDB migrations (Mongock)
Apply Mongock migration guidelines for Micronaut and Micronaut Data MongoDB.
What is covered in this Skill?
- Mongock runner/driver selection for Micronaut projects
- Micronaut bean wiring for MongoDB client access and controlled migration execution
- Code-first
@ChangeUnitmigrations with@Executionand rollback hooks - Locking, idempotency, transaction limits, and startup/runtime trade-offs
- Integration tests with
@MicronautTestand Testcontainers MongoDB - Coordination with
@515-frameworks-micronaut-mongodb
Scope: Apply recommendations based on the reference rules and good/bad examples.
Constraints
Compile before Mongock or MongoDB migration changes; verify after changes.
- MANDATORY: Run
./mvnw compileormvn compilebefore applying any change - SAFETY: If compilation fails, stop immediately
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter applying improvements - BEFORE APPLYING: Read the reference for detailed rules and good/bad patterns
- EDGE CASE: If a Micronaut-specific Mongock runner is unavailable or incompatible, use an explicit standalone runner bean/job and document that trade-off
When to use this skill
- Add Mongock migrations in Micronaut
- Review Micronaut MongoDB data migrations
- Configure Mongock change units with Micronaut Data MongoDB
- Create Mongock change units for Micronaut MongoDB
- Review Mongock migration ordering in a Micronaut service
Workflow
- Read references and inspect MongoDB setup
Read references/516-frameworks-micronaut-mongodb-migrations-mongock.md, references/516-frameworks-micronaut-mongodb-migrations-mongock-antipatterns.md, and references/516-frameworks-micronaut-mongodb-migrations-mongock-parallel-change.md, then inspect pom.xml, Micronaut MongoDB configuration, and existing @515-frameworks-micronaut-mongodb persistence patterns.
- Choose runner, driver, and execution policy
Select compatible Mongock coordinates, wire the runner through Micronaut beans, configure migration scan packages, and decide startup vs controlled-job execution.
What ships with it
3 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.
- 8d ago First seen · 67 lines · 135 tokens per session scan A 4e5bfde722cd
516-frameworks-micronaut-mongodb-migrations-mongock is a skill published in the GitHub repository jabrena/plinth (438 stars, last pushed today), licensed Apache-2.0. It adds 135 tokens to every session and 879 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
kit-nosql
NoSQL guardrails pack — MongoDB $set/replace and schema drift, Redis SCAN/TTL/atomicity, eventual consistency. Use when writing MongoDB, Redis, DynamoDB, or other non-relational store code.
jpa-patterns
JPA/Hibernate patterns and common pitfalls (N+1, lazy loading, transactions, queries). Use when user has JPA performance issues, LazyInitializationException, or asks about entity relationships and fetching strategies.
ecto-patterns
Ecto patterns — schemas, changesets, queries, migrations, Multi, associations, preloads, upserts. Use when editing Repo calls, Ecto.Query, or schema fields. Skip for Ash.
phoenix-contexts
Phoenix context design — creating/splitting contexts, Scope (1.8+), Ecto.Multi, PubSub, routers, plugs, controllers. Use when editing contexts, routers, or designing boundaries.
ecto-n1-check
Detect N+1 query anti-patterns specifically — Repo calls inside Enum/for loops, missing preloads on associations. Use when N+1 is explicitly suspected, NOT for unrelated Ecto questions or wider database performance.
ecto-constraint-debug
Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data. Use when seeing uniqueconstraint, foreignkeyconstraint, or checkconstraint errors.