quarkus-service-architecture

quarkus-service-architecture is a skill for Claude Code, Codex from makifbaysal/tasktrooper. It costs 40 tokens per session (1,066 once invoked), scanned A, original, Apache-2.0.

A guide to structuring Java services built with Quarkus, a Java framework for HTTP services and applications. It separates web requests, business rules, data access, and domain objects into clear layers.

In plain words
What is it for?
Use it when creating or extending a Quarkus service with HTTP endpoints, dependency injection, validation, or Panache/JPA database access.
Why use it?
It keeps framework-specific code at the edges, so business logic stays easier to test and change. It also prevents web or database details from spreading through the whole service.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when creating or extending a Quarkus service with HTTP endpoints, dependency injection, validation, or Panache/JPA database access.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/makifbaysal/tasktrooper/quarkus-service-architecture
Install

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.

Any agent
npx skills add makifbaysal/tasktrooper --skill quarkus-service-architecture
Clone the repo
git clone --depth 1 https://github.com/makifbaysal/tasktrooper

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for quarkus-service-architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/quarkus-service-architecture/github.svg)](https://agentmods.dev/skills/makifbaysal/tasktrooper/quarkus-service-architecture)
Your own site
<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/quarkus-service-architecture"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/quarkus-service-architecture/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.

agentmods 80×15 button for quarkus-service-architecture

Your own site · 80×15
<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/quarkus-service-architecture"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/quarkus-service-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,066 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.01066
Opus 5.5 $0.00016 $0.00426
Sonnet 5.5 $0.00008 $0.00213
Haiku 4.5 $0.00004 $0.00107

Measured 8d ago against content hash cddb9398ba4a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

quarkus-service-architecture 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 8d 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.

catalog/agents/backend-developer/skills/quarkus-service-architecture/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Quarkus Service Architecture

Overview

Quarkus is the default Java stack: fast startup, low memory, native-image friendly — the closest Java gets to Go's operational profile. Build services in clean layers so the framework stays at the edges and the domain stays plain Java.

Core principle: Framework annotations live at the boundaries (resources, repositories). The domain and services are plain classes you can unit-test without booting Quarkus.

Layers

Layer Responsibility Quarkus surface
Resource HTTP in/out, validation, status codes @Path, JAX-RS (@GET/@POST), @Valid
Service Use-case orchestration, business rules @ApplicationScoped CDI bean, constructor-injected
Domain Entities, value objects, invariants plain Java, no annotations driving behavior
Repository Persistence Panache (PanacheRepository) or JPA

Dependencies point inward: resource → service → domain; repository implements a port the service depends on. A resource never contains business logic; a service never touches RoutingContext or JAX-RS types.

Patterns

  • Constructor injection, not field injection: public TaskService(TaskRepository repo). Constructor injection is testable without CDI and makes dependencies explicit.
  • DTOs at the edge: resources accept/return DTOs (records), map to/from domain in the service. Never expose JPA entities directly over HTTP.
  • Bean Validation on request DTOs (@NotNull, @Size(max=200)) + @Valid on the resource method — validate at the boundary, reject early.
  • Reactive vs imperative: default to imperative (Quarkus REST — formerly branded "RESTEasy Reactive" — with blocking) unless the task is genuinely reactive; don't sprinkle Uni/Multi without cause. A blocking-I/O-heavy endpoint on Java 21+ may run on a virtual thread instead (@RunOnVirtualThread) rather than going reactive.
  • Config via @ConfigProperty from application.properties/env — never hardcode. Group related settings with @ConfigMapping instead of a pile of individual @ConfigProperty fields.
  • Error mapping centrally with @ServerExceptionMapper, returning RestResponse<ProblemDto> (or the repo's equivalent) — not a try/catch per resource method (api-design-conventions has the shape).
  • Dev Services start a throwaway Postgres automatically in dev/test when no quarkus.datasource.jdbc.url is set — don't hand-wire a local Postgres for local iteration unless the repo has opted out.
  • Schema management outside tests is quarkus.hibernate-orm.schema-management.strategy=none (or validate); this property was renamed from quarkus.hibernate-orm.database.generation in 3.23 — use the current name unless the repo is pinned to an older Quarkus.
  • Target the current LTS (3.40, supported to 2027-09); never move a repo onto the Quarkus 4 beta in a feature task.

Read the full file on GitHub · 85 lines

Changes

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.

  1. 8d ago First seen · 85 lines · 40 tokens per session scan A cddb9398ba4a

Subscribe to this mod's changes

quarkus-service-architecture is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 1,066 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-10-05.