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-testinggit 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-testing)<a href="https://agentmods.dev/skills/kinhluan/rules-quarkus-skills/quarkus-testing"><img src="https://agentmods.dev/badge/skills/kinhluan/rules-quarkus-skills/quarkus-testing/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-testing"><img src="https://agentmods.dev/badge/skills/kinhluan/rules-quarkus-skills/quarkus-testing.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.03405 |
| Opus 5.5 | $0.00017 | $0.01362 |
| Sonnet 5.5 | $0.00009 | $0.00681 |
| Haiku 4.5 | $0.00004 | $0.00341 |
Grade A, and why
quarkus-testing 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 — 609 lines — stays where its author put it; the contents beside it link to each section on GitHub.
quarkus-testing
Keyword: quarkus-test | Platforms: gemini,claude,codex
Quarkus Testing Expert Skill - Deep knowledge of testing strategies for the Quarkus ecosystem.
Core Mandates
- Test at the Right Level: Use
@QuarkusTestfor integration,@QuarkusUnitTestfor extension testing,@QuarkusIntegrationTestfor native/artifact verification. - Mock External Dependencies: Use
@InjectMockfor CDI beans, WireMock/Testcontainers for external services. - Dev Services First: Leverage zero-config Dev Services for databases, Kafka, Redis in dev/test.
- Test Data Isolation: Each test must be independent - use
@Transactionalrollback or@TestTransaction. - Fast Feedback: Keep
@QuarkusTestsuite fast; move slow tests to@QuarkusIntegrationTest.
@QuarkusTest Fundamentals
Basic Integration Test
@QuarkusTest
class UserResourceTest {
@Test
void shouldListUsers() {
given()
.when().get("/api/users")
.then()
.statusCode(200)
.body("$.size()", greaterThanOrEqualTo(0));
}
@Test
void shouldCreateUser() {
given()
.contentType(ContentType.JSON)
.body("""
{"name": "John Doe", "email": "[email protected]"}
""")
.when().post("/api/users")
.then()
.statusCode(201)
.header("Location", containsString("/api/users/"));
}
@Test
void shouldReturn404ForMissingUser() {
given()
.when().get("/api/users/99999")
.then()
.statusCode(404)
.body("message", containsString("not found"));
}
}
Testing with Authentication
@QuarkusTest
class SecuredResourceTest {
@Test
void shouldAllowAuthenticatedAccess() {
given()
.auth().oauth2(getAccessToken("user"))
.when().get("/api/profile")
.then()
.statusCode(200);
}
@Test
void shouldRejectUnauthorizedAccess() {
given()
.when().get("/api/profile")
.then()
.statusCode(401);
}
@Test
@TestSecurity(authorizationEnabled = false)
void shouldBypassAuthForTesting() {
given()
.when().get("/api/profile")
.then()
.statusCode(200);
}
@Test
@TestSecurity(user = "admin", roles = {"admin", "user"})
void shouldTestWithSpecificRoles() {
given()
.when().get("/api/admin/dashboard")
.then()
.statusCode(200);
}
}
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 · 609 lines · 43 tokens per session scan A 47676ca53d95
quarkus-testing is a skill published in the GitHub repository kinhluan/rules-quarkus-skills (3 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 3,405 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-31.
Other skills, from other repositories
testing-patterns
Testing patterns for Spring Boot - JUnit 5, Mockito, MockMvc, Testcontainers, positive and negative test cases. Use when user asks about testing, writing tests, test coverage, or test failures.
testing-standards
Testing standards for enterprise applications. Covers naming conventions, AAA structure, mock strategies, Testcontainers, coverage targets, test execution order, flaky test detection, and test reporting.
test-generator
A skill for creating unit tests, generating mock data or objects, and analysing test coverage. Unit tests check small parts of a program in isolation.
design-patterns
Design patterns with Java examples - classic (Factory, Builder, Strategy, Observer, Decorator, Adapter) and enterprise/microservices (Saga, Outbox, CQRS). Use when user asks about patterns, designing extensible components, or distributed transaction strategies.
jpa-patterns
JPA/Hibernate patterns and common pitfalls (N+1, lazy loading, transactions, queries). Use when user has JPA performance issues, LazyInitializationException, or asks about entity relationships and fetching strategies.
logging-patterns
Java logging best practices with SLF4J, structured logging (JSON), and MDC for request tracing. Includes AI-friendly log formats for Claude Code debugging. Use when user asks about logging, debugging application flow, or analyzing logs.