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 agentmods add skills/muhammadusmangm/claude-code-best-practices/conventional-commitnpx skills add MuhammadUsmanGM/claude-code-best-practices --skill conventional-commitgit clone --depth 1 https://github.com/MuhammadUsmanGM/claude-code-best-practicesWrote 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/muhammadusmangm/claude-code-best-practices/conventional-commit)<a href="https://agentmods.dev/skills/muhammadusmangm/claude-code-best-practices/conventional-commit"><img src="https://agentmods.dev/badge/skills/muhammadusmangm/claude-code-best-practices/conventional-commit.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 | $0.00042 | $0.00462 |
| Opus 5 | $0.00021 | $0.00231 |
| Sonnet 5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
conventional-commit 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 3d 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 Commit
You are being invoked to turn the current staged diff into a single, well-formed Conventional Commits message.
Steps
- Run
git status --shortandgit diff --cached --stat. If nothing is staged, rungit diff --statand ask the user whether to stage everything or a subset. Do not guess. - Run
git diff --cached(orgit diffif nothing staged yet) to read the actual changes. - Run
git log -10 --onelineto match the repo's existing commit style (scope naming, casing). - Draft a message:
- type: one of
feat|fix|docs|refactor|perf|test|chore|build|ci|style|revert - scope: optional, derived from the top-level directory or package touched
- subject: imperative, ≤ 72 chars, no trailing period
- body: only if the why isn't obvious from the subject. Wrap at 72.
- footer:
BREAKING CHANGE:orCloses #123only when applicable
- type: one of
- Show the message to the user and ask for confirmation unless they already said "commit it" / "just commit."
- On confirmation, run
git commit -m "..."using a heredoc for multi-line bodies.
Rules
- Never include
Co-Authored-Bylines unless the user asks. - Never
git push. - Never
--amenda commit that's already been pushed. - If pre-commit hooks fail, fix the underlying issue and create a new commit. Do not
--no-verify.
Output
After committing, print the short SHA and subject line. Nothing else.
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.
- 3d ago First seen · 35 lines · 42 tokens per session scan A dfc3fb37f8c4
conventional-commit is a skill published in the GitHub repository MuhammadUsmanGM/claude-code-best-practices (76 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 462 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
commit
Stage and create a Conventional Commits message for the current change.
commit
Create a git commit for the Vision-Agents repo.
commit
Commit current changes with a clear, descriptive message.
git-commit
Create git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead.
common-feedback-reporter
Pre-write audit for skill violations: checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart/TS code or editing SKILL.md files with active project skills. Load as composite; on auto-fixed violation, also load +common/common-learning-log.
common-exploit-verification
Enforce "No Exploit, No Report" policy with PoC construction standards, false-positive filtering, and evidence collection per vulnerability class across backend, frontend, and mobile. Use when validating security findings, constructing exploit proofs, filtering false positives, or writing pentest findings.