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 kinhluan/rules-quarkus-skills --skill quarkus-debuggit clone --depth 1 https://github.com/kinhluan/rules-quarkus-skillsWrote 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/kinhluan/rules-quarkus-skills/quarkus-debug)<a href="https://agentmods.dev/skills/kinhluan/rules-quarkus-skills/quarkus-debug"><img src="https://agentmods.dev/badge/skills/kinhluan/rules-quarkus-skills/quarkus-debug/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/kinhluan/rules-quarkus-skills/quarkus-debug"><img src="https://agentmods.dev/badge/skills/kinhluan/rules-quarkus-skills/quarkus-debug.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.00043 | $0.01526 |
| Opus 5 | $0.00022 | $0.00763 |
| Sonnet 5 | $0.00009 | $0.00305 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
quarkus-debug 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 10d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
quarkus-debug
Keyword: quarkus-debug | Platforms: gemini,claude,codex
Expert AI Agent Skill for Quarkus Debugging - Advanced techniques for diagnosing and fixing issues across the entire Quarkus lifecycle, from development mode to native executables.
Core Mandates
- Dev Mode First: Always leverage
quarkus:devfor immediate feedback and live reload. - Context-Aware Debugging: Distinguish between Imperative (Blocking) and Reactive (Event Loop) contexts.
- Binary Parity: Ensure behavior consistency between JVM mode and Native Image mode.
- Augmentation Insight: Distinguish between build-time (deployment) and run-time errors.
- No-Block Rule: Never block the Event Loop during debugging unless using specific thread-aware tools.
🛠 Debugging Domains
1. Development Phase (Dev Mode)
- JPDA/Remote Debug: Default port
5005. Usequarkus.debug.hostandquarkus.debug.portto customize. - Dev UI (
/q/dev):- Inspect CDI Beans, Configuration, and Extension status.
- Use the Arc extension UI to debug dependency injection issues.
- Continuous Testing: Debug tests as they run in the background.
- Hot Reload Issues: If changes don't reflect, check
quarkus.live-reload.passwordor ClassLoader isolation settings.
2. Reactive & Asynchronous (Mutiny)
- Stack Trace Unwrapping: Reactive stack traces are often unhelpful. Use
.onFailure().invoke(Throwable::printStackTrace)or Mutiny's infrastructure tools. - Context Propagation:
- Debug
ContextNotActiveExceptionby ensuringDuplicatedContextis propagated correctly. - Use
quarkus.arc.context-propagation.enabled=true.
- Debug
- Event Loop Blocking: Enable
quarkus.vertx.warning-exception-timeto detect long-running tasks blocking the Event Loop. - Mutiny Infrastructure: Use
Infrastructure.setCanClearThreadLocals(false)carefully to debug ThreadLocal issues.
3. Native Executables (GraalVM AOT)
- AOT Issues: Most native errors are due to Reflection, Resources, or Dynamic Proxies missing from
reflect-config.json. - GraalVM Agent: Run in JVM mode with the agent to auto-generate configs:
java -agentlib:native-image-agent=config-output-dir=./config -jar target/*-runner.jar - Native Debugging: Build with
-H:GenerateDebugInfo=1and use GDB or LLDB. - Static vs Runtime Init: Debug
InitializerErrorby checkingquarkus.native.additional-build-args=--trace-class-initialization=....
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.
- 10d ago First seen · 105 lines · 43 tokens per session scan A 444957bcf362
quarkus-debug is a skill published in the GitHub repository kinhluan/rules-quarkus-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,526 once invoked, about $0.0002 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-31.
Other skills, from other repositories
static-analysis
A static-analysis skill for embedded C and C++ code. Static analysis checks source code for likely errors without running it, while MISRA-C is a set of safety-oriented rules for C software.
gdb
Debug and trace C/C++/Rust programs with the GNU Debugger (GDB) without blocking the agent. Use when you need to set tracepoints, inspect variables, or monitor a running process while staying responsive to the user.
nullaway
Guide for resolving NullAway static analysis errors. Best practices for: Passing ObservableSupplier/Supplier Dereferencing potentially @Nullable values Adding @NullMarked to Java code.
wxjava-troubleshooter
A troubleshooting guide for WxJava, a Java library used to connect applications to WeChat services. It organizes problems involving setup, access tokens, signatures, payment certificates, callbacks, data conversion, network requests, and multiple accounts.
performance-smell-detection
Detect potential code-level performance smells in Java - streams, collections, boxing, regex, object creation. Provides awareness, not absolutes - always measure before optimizing. For JPA/database performance, use jpa-patterns instead.
126-java-exception-handling
Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast principles, handling thread interruption…