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 code-authorgit 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/code-author)<a href="https://agentmods.dev/skills/kinhluan/rules-quarkus-skills/code-author"><img src="https://agentmods.dev/badge/skills/kinhluan/rules-quarkus-skills/code-author.svg" alt="Measured on agentmods" 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.00037 | $0.01003 |
| Opus 5 | $0.00018 | $0.00502 |
| Sonnet 5 | $0.00007 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
code-author 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 7d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-author ✍️
Keyword: author | Platforms: gemini,claude,codex
Expert AI Agent Skill for Code Authoring - Best practices for creating, describing, and refining code changes based on Google's Engineering Practices.
🎯 Core Mandates (The Author's Rules)
- Small CLs Only: Keep changes focused on ONE thing. Small CLs are easier to review, faster to merge, and lower risk.
- Clear Descriptions: Always explain WHAT is changing and WHY. The "How" should be evident from the code, but the "Why" is critical context.
- Risk Areas Identification: Explicitly call out parts of the code where you are unsure or where there is a high risk of side effects.
- No Refactor + Feature Mix: Never mix refactoring with new features or bug fixes. These must be separate CLs.
- Proactive Communication: Address all reviewer comments, even if you disagree. Explain your reasoning clearly and professionally.
- Self-Audit First: Run the "Self-Audit Checklist" before sending a CL for review.
🛠 Authoring Workflows
1. Planning a Change (CL)
- Isolate the Task: Can this be broken into smaller, independent steps?
- Draft the Description: Start with a one-line summary. Add context on the problem being solved.
- Identify Risks: Note any areas that need extra attention from the reviewer.
2. Writing the Code & Self-Audit
- Tests First: Ensure the change is covered by automated tests.
- Style Consistency: Follow Google Java Style.
- Self-Audit Checklist:
- Diff Minimization: Revert accidental changes (whitespace, commented-out code).
- Documentation Check: Update README, JSDoc, or JavaDoc for new exports/logic.
- Test Alignment: Ensure tests cover logic branches, not just the "happy path."
- Logic Validation: Mentally trace the execution path for edge cases (null, empty, etc.).
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.
- 7d ago First seen · 84 lines · 37 tokens per session scan A 3ac155369aa6
code-author is a skill published in the GitHub repository kinhluan/rules-quarkus-skills (3 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,003 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
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
simplify
This skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify". Reviews changed code…
adversarial-squad
Deploy a bounded, profile-loaded adversarial review squad at an SDD point-cut (post-spec, post-plan, post-tasks, pre-merge, or an ad-hoc decision) so independent doctrine lenses converge on findings one reviewer would miss. Triggers: "deploy a squad", "adversarial squad", "post-tasks anti-laziness pass", "pre-spec…
spk-gate-accept
Run the Spec Kitty accept gate for a completed mission and verify final readiness before merge.
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
superlint
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.