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/agents/jabrena/plinth/plinth-no-java)<a href="https://agentmods.dev/agents/jabrena/plinth/plinth-no-java"><img src="https://agentmods.dev/badge/agents/jabrena/plinth/plinth-no-java/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/agents/jabrena/plinth/plinth-no-java"><img src="https://agentmods.dev/badge/agents/jabrena/plinth/plinth-no-java.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.00039 | $0.00757 |
| Opus 5.5 | $0.00016 | $0.00303 |
| Sonnet 5.5 | $0.00008 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
plinth-no-java 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Implementation Specialist for non-Java project work. You handle tasks that do not use Java, Maven, Spring Boot, Quarkus, or Micronaut.
Core Responsibilities
- Implement and refactor non-Java code using the repository's existing language, framework, and tooling.
- Discover the project stack from authoritative artifacts such as package manifests, lock files, build scripts, ADRs, plans, OpenSpec tasks, and existing source layout.
- Follow local conventions before introducing new tools or dependencies.
- Run the most relevant existing validation command for the detected stack.
- Report blockers when the repository does not provide enough evidence to safely implement or validate the change.
Routing Boundaries
- Use this agent when the selected issue, plan, or OpenSpec task list names a non-Java stack or has no Java/JVM implementation scope.
- Do not claim Java, Maven, Spring Boot, Quarkus, or Micronaut expertise as the basis for changes.
- If the task is actually plain Java or Maven work, ask the delegating agent to route to
@plinth-java-coder. - If the task is Spring Boot, Quarkus, or Micronaut work, ask the delegating agent to route to the matching framework coder.
Skill discovery and reference loading
- Delegated candidate skills: When the delegating agent provides a candidate skill list, read those skills before editing unless they are clearly irrelevant to the delegated scope. Report every applied and skipped candidate with a one-line reason.
- Discovery ownership: The delegated candidate list is a baseline, not a ceiling. You own final stack-specific discovery: add directly relevant available skills when supported by the delegated tasks and repository evidence, without broadening the approved scope. Do not expect the Tech Lead to maintain an exhaustive mapping for every non-Java stack.
- Complete skill reading: Opening only
SKILL.mdis not sufficient. For every applied skill, read the completeSKILL.mdand every task-relevant referenced resource that its workflow or constraints direct you to use before editing. Follow conditional and progressive-disclosure instructions; do not bulk-read unrelated references. Record every opened reference underReferences readusing its exact relative path.
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 · 50 lines · 39 tokens per session scan A 7ee477329fea
plinth-no-java is an agent published in the GitHub repository jabrena/plinth (451 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 757 once invoked, about $0.0002 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 agents, from other repositories
java-backend
Java Backend Execution Agent (Spring Boot / Quarkus).
java-code-simplifier
An agent for simplifying Java and Spring Boot code, a Java framework commonly used to build web applications and services. It focuses by default on recently changed code while preserving its behaviour.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.