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 clubpay/ronykit --skill conventional-commitsgit clone --depth 1 https://github.com/clubpay/ronykitWrote 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/clubpay/ronykit/conventional-commits)<a href="https://agentmods.dev/skills/clubpay/ronykit/conventional-commits"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/conventional-commits.svg" alt="Measured on agentmods" 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.00036 | $0.00464 |
| Opus 5 | $0.00018 | $0.00232 |
| Sonnet 5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
conventional-commits 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.
What it actually says
Conventional Commits
Commits are a changelog and a debugging tool. Keep them atomic and describe the why, using the Conventional Commits format.
When to use
- Creating any commit or writing a commit message.
- Splitting a branch of work into reviewable, atomic commits.
Format
<type>(<optional scope>): <subject>
<optional body — the why, not the what>
<optional footer — BREAKING CHANGE:, refs #123>
- Subject: imperative mood ("add", not "added"), ≤ ~72 chars, no trailing period.
- Body: explain motivation and context; wrap at ~72 columns.
- Breaking changes:
!after type/scope (feat!:) or aBREAKING CHANGE:footer.
Types
| Type | Use |
|---|---|
feat |
New user-facing feature |
fix |
Bug fix |
refactor |
Code change with no behavior change |
perf |
Performance improvement |
docs |
Documentation only |
test |
Adding or fixing tests |
build |
Build system or dependencies |
ci |
CI configuration |
chore |
Maintenance, tooling, housekeeping |
style |
Formatting only (no logic change) |
Atomic commits
- One logical change per commit; it should build and pass tests on its own.
- Separate refactors from behavior changes into different commits.
- Don't bundle unrelated fixes; split them.
Examples
feat(auth): add refresh-token rotation
Rotate refresh tokens on every use so a leaked token is valid for at
most one request. Old tokens are revoked atomically.
refs #482
fix(parser): handle empty input without panicking
Before committing
- Review the staged diff; stage only what belongs in this commit.
- Never commit secrets, credentials, or large generated artifacts.
- Don't commit on a protected branch unless explicitly intended.
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.
- 8d ago First seen · 74 lines · 36 tokens per session scan A e6e79105ee48
conventional-commits is a skill published in the GitHub repository clubpay/ronykit (38 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 36 tokens to every session and 464 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-30.
Other skills, from other repositories
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
conventional-commit
Workflow for generating conventional commit messages following the Conventional Commits specification. MUST be invoked every time a commit is created. Guides construction of standardized commit messages with correct type, scope, description, body, and footer.
gh
Patterns for invoking the GitHub CLI (gh) from agents. Covers structured output, pagination, repo targeting, search vs list, gh api fallback.
writing-clearly-and-concisely
Apply whenever writing content a human will read — emails, documents, reports, documentation, messages, UI copy, commit messages, explanations, or any other prose. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
commit-generate
Generate bilingual (English + Traditional Chinese) commit message from git changes.
machinist
Use Machinist to create, assign, monitor, and resume software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, lifecycle labels, direct runs, or managed queue.