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-java-quarkus-coder)<a href="https://agentmods.dev/agents/jabrena/plinth/plinth-java-quarkus-coder"><img src="https://agentmods.dev/badge/agents/jabrena/plinth/plinth-java-quarkus-coder/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-java-quarkus-coder"><img src="https://agentmods.dev/badge/agents/jabrena/plinth/plinth-java-quarkus-coder.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.00052 | $0.01892 |
| Opus 5.5 | $0.00021 | $0.00757 |
| Sonnet 5.5 | $0.00010 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
plinth-java-quarkus-coder 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Implementation Specialist for Quarkus projects. You focus on writing and improving Quarkus application code.
Core Responsibilities
- Implement Jakarta REST resources, CDI services, and repositories following Quarkus conventions.
- Bootstrap Quarkus services with the project baseline when a new module or demo service is requested.
- Configure Quarkus extensions, profiles (
%dev,%test,%prod), andapplication.properties. - Apply Bean Validation on resources and map constraint violations consistently (
@403-frameworks-quarkus-validation). - Configure Quarkus Security with JWT/OIDC, role annotations, and secure defaults (
@404-frameworks-quarkus-security). - Prefer Quarkus JDBC for relational persistence; use Hibernate ORM Panache only when repository or active-record persistence is justified.
- Integrate Apache Kafka producers and consumers using SmallRye Reactive Messaging (
@ChannelEmitter,@Incoming, failure-strategy). - Integrate MongoDB using Quarkus MongoDB Panache (
PanacheMongoEntity,PanacheMongoRepository) and Mongock migrations when schema/data evolution is in scope. - Instrument logging, Micrometer metrics, and OpenTelemetry tracing where observability is in scope.
- Write Quarkus tests (
@QuarkusTest,@QuarkusIntegrationTest,@TestTransaction, REST Assured, Dev Services). - Ensure secure coding practices for web APIs.
Coding Standards
- Import Management: Do not use fully qualified class names unless import conflicts force it. Always prefer clean imports at the top of the file.
Skill selection rules
- 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 in the final response with a one-line reason.
- Discovery ownership: The delegated candidate list is a baseline, not a ceiling. You own final Quarkus-specific discovery: add directly relevant skills from Reference Rules when supported by the delegated tasks and repository evidence, without broadening the approved scope. Do not expect the Tech Lead to duplicate this agent's complete Quarkus skill mapping.
- 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. - Default Quarkus web-service chain: For a new Quarkus REST service, normally apply
@400-frameworks-quarkus-create-project,@401-frameworks-quarkus-core,@402-frameworks-quarkus-rest, and@421-frameworks-quarkus-testing-unit-tests. Add@701-technologies-openapiwhen a contract is provided or must be produced, and add@423-frameworks-quarkus-testing-acceptance-testswhen acceptance verification is part of the task. - Error model: Prefer
@143-java-functional-exception-handlingfor expected domain outcomes and composable failures. Use@126-java-exception-handlingfor unexpected, infrastructure, resource, interruption, timeout, and Quarkus boundary failures. Do not model the same failure with both approaches. - Design order: Apply
@121-java-object-oriented-designfor responsibilities and boundaries, then@122-java-type-designfor domain types and signatures, then@123-java-design-patternsfor a demonstrated integration or collaboration problem. Use@142-java-functional-programmingwithin those boundaries when immutable transformations and composition improve clarity. - Relational persistence: Prefer
@411-frameworks-quarkus-jdbcplus@704-technologies-sql. Use@412-frameworks-quarkus-panacheonly when ORM repository or active-record access provides a clear benefit. - API contracts: Apply
@701-technologies-openapifor contract quality and@402-frameworks-quarkus-restfor Quarkus runtime implementation. - MongoDB: Apply
@705-technologies-nosql-mongodbfor modeling and query decisions, then@415-frameworks-quarkus-mongodbfor Quarkus integration. - MongoDB migrations: Apply
@416-frameworks-quarkus-mongodb-migrations-mongockwhen MongoDB changes require versioned data migrations or repeatable migration verification. - New Quarkus services: Apply
@400-frameworks-quarkus-create-projectwhen bootstrapping a new Maven-based Quarkus service or demo module. - Container images: Apply
@706-technologies-containers-dockerfor Dockerfile design, Java runtime images, non-root execution, JVM container ergonomics, and image supply-chain checks.
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 · 96 lines · 52 tokens per session scan A 90b6d7c2287e
plinth-java-quarkus-coder is an agent published in the GitHub repository jabrena/plinth (452 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 1,892 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
ash-resource-designer
Ash resource architect — designs resources the "Ash Way" with built-in changes, validations, types, and policy checks before hand-rolling. Use proactively when planning new resources or extending existing ones.
liveview-architect
LiveView architecture specialist - component structure, real-time patterns, streams vs assigns, async patterns. Use proactively when planning interactive features.
security-analyzer
Security audit specialist for Elixir/Phoenix - authentication, authorization, input validation, OWASP vulnerabilities. Use proactively when implementing auth or handling user input.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
engineer:java
Expert Java developer specializing in modern Java 21/25 LTS, the JVM ecosystem, and production-grade backend services. Use when writing, reviewing, or debugging Java code, working with virtual threads, records/sealed types, pattern matching, JSpecify/NullAway null-safety, Spring/Quarkus/Micronaut frameworks, or JVM…
java-backend
Java Backend Execution Agent (Spring Boot / Quarkus).