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 agentmods add skills/t1/tdder/quarkusnpx skills add t1/tdder --skill quarkusgit clone --depth 1 https://github.com/t1/tdderWrote 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/t1/tdder/quarkus)<a href="https://agentmods.dev/skills/t1/tdder/quarkus"><img src="https://agentmods.dev/badge/skills/t1/tdder/quarkus.svg" alt="Measured on agentmods" 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 | $0.00067 | $0.00407 |
| Opus 5 | $0.00034 | $0.00204 |
| Sonnet 5 | $0.00013 | $0.00081 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
quarkus 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 5d 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
Quarkus
Quarkus-specific conventions and patterns.
Language- and build-tool-specific conventions are covered by the java and maven skills.
Choosing Quarkus Capabilities
Quarkus-specific setup is not generic build-file work.
When adding a Quarkus capability, do not start by hand-writing pom.xml or build.gradle changes.
Use this decision ladder:
- Use Quarkus-aware tools first. If dedicated Quarkus tooling is available in the environment, use it to discover the right capability, extension, or setup workflow.
- Check the
quarkusCLI next. Before editing build files by hand, check whether thequarkusCLI can create or apply the required setup. - Only then edit Maven or Gradle files manually. If you fall back to hand-written build changes, state explicitly why the higher-level Quarkus mechanisms were not suitable.
If you find yourself adding io.quarkus:* dependencies, BOM entries, or quarkus-maven-plugin configuration by hand, stop and check whether this should be done through Quarkus-aware tooling or the quarkus CLI instead.
Reference Topics
Load the referenced file when the situation matches.
| Situation | File |
|---|---|
Adding dev-only code (seeders, fake services, dev helpers): src/dev/java pattern or @IfBuildProfile |
dev-mode.md |
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.
- 5d ago First seen · 34 lines · 67 tokens per session scan A 4e87d19ed9cf
quarkus is a skill published in the GitHub repository t1/tdder (14 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 407 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
polygen
Write NEW stateful code that is verifiable from the moment it's written, instead of auditing code that already exists (that's the "polygraph" skill). Draft a contract from a feature description, author a SAM v2 strict-profile module against it (named intents/schemas/domains, keyed acceptors, reject(reason), sealed…
test-driven-development
Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.
tdd-arrange-act-assert
This skill should be used when the user asks to "structure tests", "organize test code", mentions "arrange act assert", "AAA pattern", "given when then", discusses test readability, or wants to improve test structure.
tdd-red-green-refactor
This skill should be used when the user asks to "do TDD", "write tests first", mentions "red-green-refactor", discusses test-driven development cycles, or wants to build features incrementally with tests.
tdd-test-first
This skill should be used when the user asks to "write tests first", "start with a test", mentions "test-first development", discusses writing tests before implementation, or wants to ensure code is testable by design.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.