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 112-java-maven-pluginsgit 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/112-java-maven-plugins)<a href="https://agentmods.dev/skills/jabrena/plinth/112-java-maven-plugins"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/112-java-maven-plugins/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/112-java-maven-plugins"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/112-java-maven-plugins.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.00149 | $0.03053 |
| Opus 5.5 | $0.00060 | $0.01221 |
| Sonnet 5.5 | $0.00030 | $0.00611 |
| Haiku 4.5 | $0.00015 | $0.00305 |
Grade A, and why
112-java-maven-plugins 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 23d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maven Plugins: pom.xml Configuration Best Practices
Configure Maven plugins and profiles in pom.xml using a structured, question-driven process that preserves existing configuration. This is an interactive SKILL.
What is covered in this Skill?
Maven plugins:
- Maven Compiler
- Maven Enforcer
- Maven Surefire
- Maven Failsafe
- HTML test reports (Surefire Report, JXR)
- Maven Spotless
- Maven Flatten
- Maven Versions
- Maven Git Commit ID
- Maven Jib
Maven profiles:
- JaCoCo (code coverage)
- PiTest (mutation testing)
- Security (OWASP dependency check)
- Static analysis (SpotBugs, PMD)
- SonarQube/SonarCloud
- JMH (Java Microbenchmark Harness)
- Cyclomatic complexity
Constraints
Before applying plugin recommendations, ensure the project is in a valid state. Use a structured, question-driven process that preserves existing configuration and adds only what the user selects.
- MANDATORY: Run
./mvnw validateormvn validatebefore applying any plugin recommendations - SAFETY: If validation fails, stop and ask the user to fix issues—do not proceed until resolved
- SCOPE: Begin with Step 1 (existing configuration analysis) before any changes. Never remove or replace existing plugins; only add new ones that do not conflict
- BEFORE READING PLUGIN REFERENCES: Run the question flow embedded in this SKILL.md first. Ask questions one-by-one in strict order, collect all selected plugins/profiles and conditional values, then read only the implementation references selected by the user's answers
When to use this skill
- Add Maven plugins in pom.xml
- Improve Maven plugins in pom.xml
- Configure Maven quality plugins in pom.xml
- Add Maven build lifecycle plugins for Java verification
- Review Maven plugin versions and executions
Workflow
- Validate project before plugin changes
Run ./mvnw validate or mvn validate and stop if validation fails.
- Analyze current plugin and profile configuration
Before making any changes to pom.xml:
What ships with it
19 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.
- references/112-java-maven-plugins-flatten-maven-plugin.md 4.4 KB
- references/112-java-maven-plugins-git-commit-id-maven-plugin.md 4.9 KB
- references/112-java-maven-plugins-jib-maven-plugin.md 4.6 KB
- references/112-java-maven-plugins-maven-compiler-plugin.md 4.5 KB
- references/112-java-maven-plugins-maven-dependency-plugin.md 5.4 KB
- references/112-java-maven-plugins-maven-enforcer-plugin.md 4.7 KB
- references/112-java-maven-plugins-maven-failsafe-plugin.md 4.6 KB
- references/112-java-maven-plugins-maven-jxr-plugin.md 3.4 KB
- references/112-java-maven-plugins-maven-surefire-plugin.md 4.0 KB
- references/112-java-maven-plugins-maven-surefire-report-plugin.md 3.6 KB
- references/112-java-maven-plugins-profile-cyclomatic-complexity.md 7.6 KB
- references/112-java-maven-plugins-profile-jacoco.md 7.1 KB
- references/112-java-maven-plugins-profile-jmh.md 12 KB
- references/112-java-maven-plugins-profile-pitest.md 5.9 KB
- references/112-java-maven-plugins-profile-security.md 5.4 KB
- references/112-java-maven-plugins-profile-sonar.md 5.6 KB
- references/112-java-maven-plugins-profile-static-analysis.md 5.5 KB
- references/112-java-maven-plugins-spotless-maven-plugin.md 4.5 KB
- references/112-java-maven-plugins-versions-maven-plugin.md 4.3 KB
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.
- 23d ago Changed 99201a1df3b8
- 1mo ago First seen · 268 lines · 149 tokens per session scan A 7458be5f6003
112-java-maven-plugins is a skill published in the GitHub repository jabrena/plinth (454 stars, last pushed yesterday), licensed Apache-2.0. It adds 149 tokens to every session and 3,053 once invoked, about $0.0006 per session on Opus 5.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
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.
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 +…
maven-harness-pom
Reference Maven POM fragments for the full harness — Spotless, Checkstyle, SpotBugs, Error Prone, JaCoCo, PIT, OpenAPI generator + diff, OWASP dependency check, Surefire/Failsafe. Use when wiring the harness into a new project or upgrading a brownfield POM.
archunit-rules
Encode architecture invariants as ArchUnit rules. Use when defining or reviewing layer boundaries, package dependencies, naming conventions, or cross-module access.
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…
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…