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 152-java-performance-gatlinggit 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/152-java-performance-gatling)<a href="https://agentmods.dev/skills/jabrena/plinth/152-java-performance-gatling"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/152-java-performance-gatling/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/152-java-performance-gatling"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/152-java-performance-gatling.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.00099 | $0.00941 |
| Opus 5 | $0.00049 | $0.00470 |
| Sonnet 5 | $0.00020 | $0.00188 |
| Haiku 4.5 | $0.00010 | $0.00094 |
Grade A, and why
152-java-performance-gatling 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 5d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run performance tests based on Gatling
Provide a complete Gatling performance testing setup for Java Maven projects by adding the required test dependencies and Gatling Maven plugin configuration, creating or guiding Java simulation placement, and explaining how to run simulations and inspect reports.
What is covered in this Skill?
- Add Gatling dependencies and the
gatling-maven-plugintopom.xml - Project structure:
src/test/javafor Java simulations andsrc/test/resourcesfor Gatling configuration, feeders, templates, and logging - Run simulations with
./mvnw gatling:test - Select a simulation with
-Dgatling.simulationClass=<FullyQualifiedClassName>when multiple simulations exist - Use
./mvnw gatling:help -Ddetail=true -Dgoal=testto inspect available plugin options - Review generated Gatling run output and reports under the build output directory
Scope: Use Gatling through the Maven plugin for Java simulations. Prefer project-local Maven wrapper commands when available.
Constraints
Gatling setup must be Maven-based, reproducible, and compatible with Java project conventions. Prefer official Gatling Maven plugin behavior and avoid inventing unsupported command-line options.
- PREREQUISITE: Verify the project is Maven-based and prefer
./mvnwwhen the Maven wrapper exists - BUILD CONFIGURATION: Add Gatling dependencies with test scope and configure
io.gatling:gatling-maven-plugininpom.xml - VERSION SELECTION: Use the project's existing dependency/version-management pattern; if no Gatling versions are present, ask before pinning versions or use placeholders that require replacement
- SIMULATION LOCATION: Place Java simulations under
src/test/javausing an appropriate package name - RESOURCE LOCATION: Place Gatling resources such as
gatling.conf, feeders, request-body templates, and Logback test configuration undersrc/test/resources - BEFORE APPLYING: Read the reference for setup, execution, and verification guidance
- EDGE CASE: If the project is not Maven-based, stop and explain that this skill targets Maven projects before suggesting Gradle or sbt alternatives
- EDGE CASE: If multiple simulations exist, configure or pass
-Dgatling.simulationClass=<FullyQualifiedClassName>for non-interactive execution
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.
- 5d ago First seen · 74 lines · 99 tokens per session scan A b4fec9a63440
152-java-performance-gatling is a skill published in the GitHub repository jabrena/plinth (437 stars, last pushed yesterday), licensed Apache-2.0. It adds 99 tokens to every session and 941 once invoked, about $0.0005 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
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.
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…
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 +…
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".
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…