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 andrewsrigom/agent-skills --skill setup-conventional-commitsgit clone --depth 1 https://github.com/andrewsrigom/agent-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/andrewsrigom/agent-skills/setup-conventional-commits)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/setup-conventional-commits"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/setup-conventional-commits/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/andrewsrigom/agent-skills/setup-conventional-commits"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/setup-conventional-commits.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.00056 | $0.00794 |
| Opus 5 | $0.00028 | $0.00397 |
| Sonnet 5 | $0.00011 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
setup-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 9d 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.
Setup Conventional Commits
Use this skill when the task is to enforce Conventional Commits in a repo with minimal friction.
Scope
commitlintsetup- Husky
commit-msghook setup - local
commit-msgenforcement - choosing a minimal config
- keeping commit flow lightweight
Routing cues
- enforce semantic commits, add commitlint, set up conventional commits, validate commit messages, or add a
commit-msghook -> use this skill - if the task is about naming one specific commit well -> use
write-intentional-commit-message - if the task is mainly about broader pre-commit automation -> use
setup-pre-commit
Default path
- Use Conventional Commits as the history format.
- Use
@commitlint/cliwith@commitlint/config-conventional. - Prefer one small config file such as
commitlint.config.cjs. - Add a
commit-msghook through Husky when the repo accepts local hook tooling. - Keep enforcement syntax-focused in tooling and intent-focused in docs or agent guidance.
When to deviate
- Extend the default type rules only when the repo has a real semantic need, not just personal preference.
- Skip Husky if the repo deliberately avoids local Git hook tooling.
- Add prompts or commit generators only when the team explicitly wants them; do not make them the default.
Guardrails
- keep the config minimal
- syntax enforcement should not pretend to solve poor commit intent by itself
- do not add
commitizenor other interactive tooling unless the repo actually wants that ceremony commit-msgvalidation is the right hook for commit format; do not overloadpre-commit
Avoid
- introducing a large commit workflow stack for a small repo
- forcing interactive commit tooling when plain Git is enough
- adding extra enforcement layers when the local hook already solves the problem
- treating enforcement as complete when contributors still have no guidance on type selection
Verification checklist
- the repo has one clear Conventional Commit policy
- commitlint config is minimal and readable
commit-msgis used for message validation if local hooks are enabled- contributors still have guidance on choosing the right type, not only passing syntax
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.
- 9d ago First seen · 84 lines · 56 tokens per session scan A f1aee12ad909
setup-conventional-commits is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 794 once invoked, about $0.0003 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…