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 eldermoraes/quarkus-agentic-scaffolding --skill audit-projectgit clone --depth 1 https://github.com/eldermoraes/quarkus-agentic-scaffoldingWrote 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/eldermoraes/quarkus-agentic-scaffolding/audit-project)<a href="https://agentmods.dev/skills/eldermoraes/quarkus-agentic-scaffolding/audit-project"><img src="https://agentmods.dev/badge/skills/eldermoraes/quarkus-agentic-scaffolding/audit-project/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/eldermoraes/quarkus-agentic-scaffolding/audit-project"><img src="https://agentmods.dev/badge/skills/eldermoraes/quarkus-agentic-scaffolding/audit-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.03686 |
| Opus 5 | $0.00045 | $0.01843 |
| Sonnet 5 | $0.00018 | $0.00737 |
| Haiku 4.5 | $0.00009 | $0.00369 |
Grade A, and why
audit-project 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 today.
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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit a Quarkus + LangChain4j Project
Version: 0.23.3
Gate: verify the MCP first
Do this before anything else — before reading the project, before §1. An audit is Quarkus
work, so the Quarkus Agents MCP is mandatory (conventions §1). VERIFY it is reachable: confirm the
quarkus_* tools are present in your toolset and that a cheap call (e.g. quarkus_status)
succeeds. If the tools are absent or the call fails, STOP immediately: report exactly what is
missing, point the user to /setup-agentic-scaffolding (and to restarting the session after
registering it, since MCPs load at session start), and end the turn. A missing or unreachable MCP
is never permission to proceed manually — do not fall back to the Quarkus CLI, model memory, or web
search, and do not offer to "continue without it". Only once the gate passes do you continue below.
1. When to use this skill
Use this skill to review an existing project against the Quarkus + LangChain4j agentic
conventions and report where it conforms and where it drifts. It never creates or scaffolds — for
that, use /scaffold-project; to configure prerequisites, use /setup-agentic-scaffolding.
Invoke it as /audit-project (skills-CLI install) or /quarkus-agentic-scaffolding:audit-project (plugin
install) — both name the same skill.
Required tooling (mandatory). This skill needs the Quarkus Agents MCP (for version-matched
validation via quarkus_skills / quarkus_searchDocs with projectDir); if it is absent or
unreachable, stop per the gate above. context7 backs any library or framework API question the
checks raise. The project's conventions file (CLAUDE.md / AGENTS.md / GEMINI.md) is the
preferred source of truth for the checks — but a missing conventions file does not stop the
audit: record it as a HIGH finding (§5.0) and audit against this skill's §5 catalog directly,
which covers the core of the canonical conventions. Do not fall back to model memory or a generic
web search.
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.
- today Changed 7a07b7de3df1
- 11d ago First seen · 205 lines · 90 tokens per session scan A 973dc9bfa2c4
audit-project is a skill published in the GitHub repository eldermoraes/quarkus-agentic-scaffolding (26 stars, last pushed yesterday), licensed Apache-2.0. It adds 90 tokens to every session and 3,686 once invoked, about $0.0005 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
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
codex-ab
Run an A/B codex review experiment — holistic codex review vs 3 focused dimension passes (security, ecto, liveview) on the branch diff, classify findings, report a panel-value verdict. Use when the branch is fresh, before any codex review runs.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.