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/profile)<a href="https://agentmods.dev/commands/jabrena/plinth/profile"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/profile/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/profile"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/profile.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.00411 |
| Opus 5.5 | $0.00004 | $0.00164 |
| Sonnet 5.5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
profile 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
profile
Coordinate a Java profiling lifecycle from reproducible baseline through evidence-backed optimization verification.
Usage
/profile <application-or-module> [issue|plan|openspec-change|suspected-problem] [runtime-command] [workload]
Accepted inputs
- Application, module, or repository path
- Optional issue, implementation plan, OpenSpec change, or suspected performance problem
- Runtime command and representative workload
- Optional existing baseline or profiling artifacts
Owner and skills
- Owner:
@plinth-java-performance - Associated skills:
@161-java-profiling-detect,@162-java-profiling-analyze,@163-java-profiling-refactor, and@164-java-profiling-verify
Workflow
- Record runtime, environment, workload, and baseline metadata.
- Use profiling detection to collect reproducible evidence.
- Analyze hotspots and rank findings by impact, confidence, and risk.
- Ask for user approval before selecting an optimization target.
- Delegate application-code changes to the appropriate Java/framework coder agent.
- Repeat an equivalent measurement and compare against the baseline.
- Report the outcome as verified, inconclusive, or regressed with evidence.
Output
- Baseline metadata
- Profiling artifacts and findings
- Prioritized optimization recommendation
- Delegation record
- Before/after comparison
- Verified, inconclusive, or regressed outcome
Safeguards
- Do not optimize without user approval.
- Do not claim improvement from non-equivalent measurements.
- Do not let
@plinth-java-performanceimplement application-code changes directly. - Keep baseline, evidence, delegation, and verification artifacts traceable.
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 · 60 lines · 10 tokens per session scan A 00ce8c3a4329
profile is a command published in the GitHub repository jabrena/plinth (451 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 411 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
analyze-java-domain-flow
A command for analyzing how calls move through a Java Spring Boot project and producing a flow diagram in one file. Java is a programming language, and Spring Boot is a framework for building Java applications.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.