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.
git 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/commands/jabrena/plinth/benchmark)<a href="https://agentmods.dev/commands/jabrena/plinth/benchmark"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/benchmark/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/commands/jabrena/plinth/benchmark"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/benchmark.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00010 | $0.00438 |
| Opus 5.5 | $0.00004 | $0.00175 |
| Sonnet 5.5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
benchmark 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 1mo 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.
What it actually says
benchmark
Select and coordinate an appropriate Java performance test with reproducible workload, environment, thresholds, and result artifacts.
Usage
/benchmark <target> [objective-or-threshold] [workload] [environment] [preferred-tool]
Accepted inputs
- Target application, endpoint, workflow, method, or component
- Performance objective or threshold
- Expected workload and environment
- Optional preferred tool
Owner and skills
- Owner:
@plinth-java-performance - Associated skills:
@151-java-performance-jmeter,@152-java-performance-gatling, and existing Maven/JMH guidance
Tool selection
| Need | Tool |
|---|---|
| HTTP/API load and performance test | JMeter or Gatling |
| Scenario-oriented load model and reports | Gatling |
| Isolated JVM method or component microbenchmark | JMH |
Workflow
- Clarify target boundary, objective, thresholds, workload, and environment.
- Select JMeter, Gatling, or JMH and record the rationale.
- Define warm-up, duration, concurrency, data setup, and result artifacts.
- Generate or coordinate the reproducible performance workflow using the selected skill or Maven/JMH guidance.
- Evaluate results against explicit thresholds.
- Report limitations, environment metadata, and whether results are comparable.
Output
- Selected tool and rationale
- Reproducible test configuration
- Baseline or result artifacts
- Threshold assessment
- Limitations and environment metadata
Safeguards
- Do not present non-equivalent runs as valid before/after comparisons.
- Do not use JMeter or Gatling for isolated JVM microbenchmarks when JMH is the correct boundary.
- Do not use JMH for end-to-end load behavior.
- Keep workload, environment, and threshold assumptions explicit.
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.
- 1mo ago First seen · 66 lines · 10 tokens per session scan A d02a1835bec6
benchmark is a command published in the GitHub repository jabrena/plinth (452 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 438 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
test
Run /test — see .claude/commands/test.md for the authoritative spec.
justfile-recipe-short-doc
Shorten justfile recipe doc comments for simple recipes.
test-cases
Use when writing test cases, generating tests, supplementing test coverage, or improving test completeness — auto-scans project, designs multi-dimensional test cases with coverage matrix.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.