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.
npx skills add jabrena/plinth --skill 400-frameworks-quarkus-create-projectgit 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/skills/jabrena/plinth/400-frameworks-quarkus-create-project)<a href="https://agentmods.dev/skills/jabrena/plinth/400-frameworks-quarkus-create-project"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/400-frameworks-quarkus-create-project/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/skills/jabrena/plinth/400-frameworks-quarkus-create-project"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/400-frameworks-quarkus-create-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00094 | $0.00681 |
| Opus 5 | $0.00047 | $0.00341 |
| Sonnet 5 | $0.00019 | $0.00136 |
| Haiku 4.5 | $0.00009 | $0.00068 |
Grade A, and why
400-frameworks-quarkus-create-project 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 7d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Quarkus Maven Project
Create a new Quarkus Maven project through SDKMAN-managed tooling, aligned with Java 25 and the repository's Quarkus 3.x baseline.
What is covered in this Skill?
- Verify SDKMAN and Java availability before project creation
- Install or select the required Java and Quarkus CLI candidates through SDKMAN
- Gather project coordinates, package name, Java version, extensions, and target directory
- Create a Maven project with the Quarkus CLI
- Prefer Maven wrapper commands for validation
- Verify the generated project with Maven before reporting completion
Constraints
Project creation must be explicit, reproducible, and Maven-based.
- PREREQUISITE: Verify SDKMAN is installed with
sdk version; if missing, stop and provide setup guidance instead of installing it silently - JAVA BASELINE: Prefer Java 25 unless the user requests another supported version
- FRAMEWORK BASELINE: Target the current Quarkus 3.x line by default
- BUILD TOOL: Generate a Maven project, not Gradle
- SAFETY: Do not overwrite an existing non-empty target directory without explicit user confirmation
- VERIFY: Run
./mvnw clean verifyfrom the generated project when the Maven wrapper exists; otherwise runmvn clean verify - BEFORE APPLYING: Read the reference for the full SDKMAN and Quarkus CLI workflow
When to use this skill
- Create a Quarkus Maven project
- Bootstrap Quarkus project with SDKMAN
- Generate a new Quarkus service
- Create Quarkus 3 Maven project
- Scaffold Quarkus service with Java 25
Workflow
- Read reference and gather project inputs
Read references/400-frameworks-quarkus-create-project.md, then gather project directory, group, artifact, package name, Java version, and desired Quarkus extensions.
- Verify SDKMAN-managed tooling
Check SDKMAN, Java, and Quarkus CLI availability. Install or switch candidates only after confirming the intended versions with the user.
- Create the Maven project
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 63 lines · 94 tokens per session scan A 70cea4cae68f
400-frameworks-quarkus-create-project is a skill published in the GitHub repository jabrena/plinth (438 stars, last pushed yesterday), licensed Apache-2.0. It adds 94 tokens to every session and 681 once invoked, about $0.0005 per session on Opus 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-09-03.
Other skills, from other repositories
spring-boot-engineer
Generates Spring Boot 3.x configurations, creates REST controllers, implements Spring Security 6 authentication flows, sets up Spring Data JPA repositories, and configures reactive WebFlux endpoints. Use when building Spring Boot 3.x applications, microservices, or reactive Java applications; invoke for Spring Data…
spring-boot-patterns
Spring Boot best practices and patterns. Use when creating controllers, services or repositories, or when the user asks about Spring Boot layering, wiring, configuration or exception handling. For JPA and Hibernate behaviour, use jpa-patterns instead.
api-contract-review
Review REST API contracts for HTTP semantics, versioning, backward compatibility, and response consistency. Use when user asks "review API", "check endpoints", "REST review", or before releasing API changes.
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.