Agent skill

151 Java Performance Jmeter

by jabrena in jabrena/plinth

A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…

Apache-2.0Auto-check passedTesting & QA

Install 151 Java Performance Jmeter

skills CLI
$ npx skills add jabrena/plinth --skill 151-java-performance-jmeter -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jabrena/plinth 151-java-performance-jmeter --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/151-java-performance-jmeter .claude/skills/151-java-performance-jmeter && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
151-java-performance-jmeter
GitHub stars
446
Token cost
~842 tokens
SKILL.md length
342 words
Files
3 (incl. scripts, references)
Skills in repo
124
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…

  • You need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template
  • SKILL.md covers Constraints, When to use this skill, Workflow and Reference
  • Runs Shell scripts from its folder
  • Configuring load tests with loops

What it does

151 Java Performance Jmeter is an agent skill from jabrena/plinth. Use when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with loops, threads, and ramp-up, or running performance tests from the project root with custom or default settings. This should trigger for requests such as Improve the code with JMeter performance testing; Apply JMeter performance testing; Refactor the code with JMeter performance testing; Add JMeter support; Create a JMeter test plan for a Java…

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/151-java-performance-jmeter.md` and `scripts/run-jmeter.sh`).

It sits in Testing & QA, covering Load testing. It works with Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

  • You need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template
  • Configuring load tests with loops
  • Running performance tests from the project root with custom
  • Default settings

Example prompts

  • “/151-java-performance-jmeter”

Requirements

  • A Bash shell

What it can do on your machine

Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

151 Java Performance Jmeter loads about 842 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 145 tokens; SKILL.md has 342 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~145
When it runs · the whole SKILL.md, loaded when a task matches
~842
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 342 words, ~842 tokens.

Download SKILL.mdSave it as .claude/skills/151-java-performance-jmeter/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
151-java-performance-jmeter
description
Use when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with loops, threads, and ramp-up, or running performance tests from the project root with custom or default settings. This should trigger for requests such as Improve the code with JMeter performance testing; Apply JMeter performance testing; Refactor the code with JMeter performance testing; Add JMeter support; Create a JMeter test plan for a Java service. Part of Plinth Toolkit
license
Apache-2.0
metadata.author
Juan Antonio Breña Moral
metadata.version
0.19.0

Run performance tests based on JMeter

Provide a complete JMeter performance testing solution by creating the run-jmeter.sh script from the exact template, making it executable, and configuring the project structure for load testing. Supports custom loops, threads, ramp-up, and environment variable overrides.

What is covered in this Skill?

  • Create run-jmeter.sh in project root from the exact template (no modifications)
  • Project structure: src/test/resources/jmeter/load-test.jmx, target/ for results
  • Script options: -l (loops), -t (threads), -r (ramp-up), -g (GUI), -h (help)
  • Environment variables: JMETER_LOOPS, JMETER_THREADS, JMETER_RAMP_UP
  • Verify JMeter is installed and available before proceeding

Scope: Copy the script template verbatim. Do not modify, interpret, or enhance the template content.

Constraints

JMeter must be installed and available in PATH. If not available, show a message and exit. Use only the exact template for the run-jmeter.sh script.

  • PREREQUISITE: Verify JMeter is installed and accessible via jmeter --version before creating the script
  • CRITICAL: Copy the run-jmeter.sh template exactly — do not modify, interpret, or enhance
  • PERMISSION: Make the script executable with chmod +x run-jmeter.sh
  • BEFORE APPLYING: Read the reference for the exact script template and usage instructions
  • 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

  • Improve the code with JMeter performance testing
  • Apply JMeter performance testing
  • Refactor the code with JMeter performance testing
  • Add JMeter support
  • Create a JMeter test plan for a Java service

Workflow

  1. Verify JMeter prerequisite

Check jmeter --version and stop with guidance if JMeter is not installed or not available in PATH.

  1. Read JMeter reference template

Read references/151-java-performance-jmeter.md and use the run-jmeter.sh template exactly as provided.

  1. Create script and project structure

Create run-jmeter.sh in project root, ensure required JMeter directories/files exist, and apply executable permission with chmod +x.

  1. Explain usage and environment overrides

Document CLI options (-l, -t, -r, -g, -h) and environment variable overrides (JMETER_LOOPS, JMETER_THREADS, JMETER_RAMP_UP).

Reference

For detailed guidance, examples, and constraints, see references/151-java-performance-jmeter.md.

© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts, references) in skills/151-java-performance-jmeter of jabrena/plinth.

  • SKILL.md
  • references/151-java-performance-jmeter.md
  • scripts/run-jmeter.sh

Open the folder on GitHubat commit dca88dc

Compare with similar skills

151 Java Performance Jmeter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

151 Java Performance Jmeter compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
151 Java Performance Jmeter this skilljabrena/plinth446—~842Automated safety check: PassApache-2.0
Afrexai Performance EngineeringLeoYeAI/openclaw-master-skills2.2k—~7.1kAutomated safety check: PassMIT
Java SDK E2E Test with Replay Snapshotgithub/copilot-sdk11k—~1.8kAutomated safety check: PassMIT
Find Untested Sourcesdotnet/skills5.6k1 repos~3.3kAutomated safety check: PassMIT
Microbenchmarkingdotnet/skills5.6k3 repos~3.3kAutomated safety check: PassMIT
Control UI E2Eopenclaw/openclaw392k—~2.9kAutomated safety check: PassMIT

Similar skills

  • Afrexai Performance Engineering

    LeoYeAI/openclaw-master-skills

    Complete performance engineering system — profiling, optimization, load testing, capacity planning, and performance culture.

    2.2k GitHub stars~7.1k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Official

    Creates a Java SDK end-to-end test for the Copilot SDK that runs against a recorded YAML snapshot through a replay proxy, so CI needs no real authentication.

    11k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed
  • Official

    Statically pairs source files with test files to list code that no test references, using Roslyn for C# or tree-sitter for many languages, with no build.

    5.6k GitHub starsUsed in 1 repo~3.3k tokens
    Testing & QAAuto-check passed
  • Microbenchmarking

    dotnet/skills

    Official

    Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks.

    5.6k GitHub starsUsed in 3 repos~3.3k tokens
    Testing & QAAuto-check passed
  • Control UI E2E

    openclaw/openclaw

    A skill your agent uses when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks…

    392k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Omnigent Load Test Runner

    omnigent-ai/omnigent

    Runs the Omnigent load test with real hosts and multi-turn sessions against a mocked LLM, then explains the latency results from summary.md.

    11k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed

More from jabrena/plinth

All 124 skills in this repo
  • A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    446 GitHub stars~874 tokensUpdated today
    Auto-check passed
  • A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…

    446 GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…

    446 GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…

    446 GitHub stars~903 tokensUpdated today
    Auto-check passed
  • A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…

    446 GitHub stars~697 tokensUpdated today
    Auto-check passed
  • 002 Agents Inventory

    jabrena/plinth

    A skill your agent uses when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project…

    446 GitHub stars~675 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about 151 Java Performance Jmeter

What does 151 Java Performance Jmeter do?

A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…. 151 Java Performance Jmeter is an agent skill from jabrena/plinth.sh script from the exact template, configuring load tests with loops, threads, and ramp-up, or running performance tests from the project root with custom or default settings.

When should I use 151 Java Performance Jmeter?

151 Java Performance Jmeter fits situations like: you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template; configuring load tests with loops; running performance tests from the project root with custom; default settings.

How do I install 151 Java Performance Jmeter in Claude Code?

Run `npx skills add jabrena/plinth --skill 151-java-performance-jmeter -a claude-code`. Or copy the skill folder (skills/151-java-performance-jmeter in jabrena/plinth) into .claude/skills/151-java-performance-jmeter in your project. Claude Code loads it when a task matches its description.

How do I install 151 Java Performance Jmeter in Codex?

Run `npx skills add jabrena/plinth --skill 151-java-performance-jmeter -a codex`. Or copy the skill folder (skills/151-java-performance-jmeter in jabrena/plinth) into .agents/skills/151-java-performance-jmeter in your project. Codex loads it when a task matches its description.

Can I use 151 Java Performance Jmeter in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 151-java-performance-jmeter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/151-java-performance-jmeter, .gemini/skills/151-java-performance-jmeter, .github/skills/151-java-performance-jmeter and .opencode/skills/151-java-performance-jmeter in your project.

What does 151 Java Performance Jmeter need to run?

Going by SKILL.md and its folder, 151 Java Performance Jmeter needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does 151 Java Performance Jmeter access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is 151 Java Performance Jmeter safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does 151 Java Performance Jmeter use?

151 Java Performance Jmeter is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 151 Java Performance Jmeter use?

About 842 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to 151 Java Performance Jmeter?

Skills that share tags, products or a category with 151 Java Performance Jmeter: Afrexai Performance Engineering (LeoYeAI/openclaw-master-skills, 2.2k stars), Java SDK E2E Test with Replay Snapshot (github/copilot-sdk, 11k stars), Find Untested Sources (dotnet/skills, 5.6k stars) and Microbenchmarking (dotnet/skills, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 151 Java Performance Jmeter?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 446 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.