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 microprofile-expertgit 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/microprofile-expert)<a href="https://agentmods.dev/skills/kinhluan/rules-quarkus-skills/microprofile-expert"><img src="https://agentmods.dev/badge/skills/kinhluan/rules-quarkus-skills/microprofile-expert/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/microprofile-expert"><img src="https://agentmods.dev/badge/skills/kinhluan/rules-quarkus-skills/microprofile-expert.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.00038 | $0.03467 |
| Opus 5 | $0.00019 | $0.01733 |
| Sonnet 5 | $0.00008 | $0.00693 |
| Haiku 4.5 | $0.00004 | $0.00347 |
Grade A, and why
microprofile-expert 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 11d 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 — 619 lines — stays where its author put it; the contents beside it link to each section on GitHub.
microprofile-expert
Keyword: microprofile | Platforms: gemini,claude,codex
MicroProfile Expert Skill - Deep knowledge of Eclipse MicroProfile specifications for building cloud-native microservices.
Core Mandates
- Config Externalization: All environment-specific values must use
@ConfigProperty, never hardcode. - Health Probes: Always implement both
@Livenessand@Readinesschecks for container orchestration. - Metrics Exposure: Expose application metrics via
@Timed,@Counted,@Meteredfor observability. - API Documentation: Auto-generate OpenAPI specs from code annotations.
- Fault Tolerance: Use
@Retry,@CircuitBreaker,@Timeout,@Fallbackfor resilient services. - Security First: Use MicroProfile JWT for stateless authentication in microservices.
MicroProfile Config
@ConfigProperty
@ApplicationScoped
public class PaymentConfig {
@ConfigProperty(name = "payment.timeout", defaultValue = "30")
int timeoutSeconds;
@ConfigProperty(name = "payment.gateway.url")
String gatewayUrl; // Required - fails if missing
@ConfigProperty(name = "payment.api-key")
Optional<String> apiKey; // Optional
@ConfigProperty(name = "payment.features")
Optional<List<String>> features; // Comma-separated list
@ConfigProperty(name = "payment.enabled", defaultValue = "true")
boolean enabled;
}
Config Sources Priority
1. System properties (-Dpayment.timeout=60)
2. Environment variables (PAYMENT_TIMEOUT=60)
3. application.properties / application.yaml
4. META-INF/microprofile-config.properties
5. Custom ConfigSource implementations
Custom ConfigSource
@Priority(400)
public class DatabaseConfigSource implements ConfigSource {
@Override
public Map<String, String> getProperties() {
// Load from database
return Map.of(
"db.host", "postgres.internal",
"db.port", "5432"
);
}
@Override
public String getValue(String propertyName) {
return getProperties().get(propertyName);
}
@Override
public String getName() {
return "DatabaseConfigSource";
}
@Override
public int getOrdinal() {
return 400; // Higher = higher priority
}
}
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.
- 11d ago First seen · 619 lines · 38 tokens per session scan A 519c7e231664
microprofile-expert is a skill published in the GitHub repository kinhluan/rules-quarkus-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 3,467 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
fastapi
FastAPI best practices and conventions. Use when working with FastAPI APIs, Pydantic models, dependencies, streaming responses including Server-Sent Events (SSE), and serving frontend apps. Keeps FastAPI code clean and up to date with the latest features and patterns.
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a…
implementing-api-schema-validation-security
Implement API schema validation using OpenAPI specifications and JSON Schema to enforce input/output contracts and prevent injection, data exposure, and mass assignment attacks.
implementing-jwt-signing-and-verification
JSON Web Tokens (JWT) defined in RFC 7519 are compact, URL-safe tokens used for authentication and authorization in web applications. This skill covers implementing secure JWT signing with HMAC-SHA256.
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…