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 vmkteam/claude-plugins --skill commit-msggit clone --depth 1 https://github.com/vmkteam/claude-pluginsWrote 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/vmkteam/claude-plugins/commit-msg)<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/commit-msg"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/commit-msg/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/vmkteam/claude-plugins/commit-msg"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/commit-msg.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.00045 | $0.00507 |
| Opus 5.5 | $0.00018 | $0.00203 |
| Sonnet 5.5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
commit-msg 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 23d 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
Generate a concise commit message in English from all current changes: staged, unstaged, and new files.
- Format and lint first, only when the project supports it: if
make -n fmt lint >/dev/null 2>&1succeeds (a Makefile with both targets exists), runmake fmt lint— formatting can change files, so read the diff after it. No Makefile or no such targets — skip with one line saying so. Skip it too if fmt and lint already passed after the last code change (for example, /solve just ran them). If lint fails, don't fix the code in this step and don't stop: write the message anyway and list the lint errors after it. - Run
git diff --cached,git diffandgit status --short. Untracked files don't appear in diffs — read new files that will be committed. If only part of the changes is staged, say which files are not staged. - Subject line: the ticket ID from the branch name (if present), a space, then the summary:
PLF-852 Add .... The summary is at most 50 characters, not counting the ticket prefix; the whole line never exceeds 72. Capitalized, no period at the end, imperative mood ("Add", "Fix", "Remove" — not "Added", "Fixed"). - If the summary doesn't fit, keep the main change in the subject and move the rest to the body.
- Separate subject from body with a blank line.
- Body: bullet points on what changed and why (not how), wrapped at 72 chars. Group related changes, mention bug fixes with "Fix".
- Output only the commit message, plus the lint errors from step 0 if there were any.
Style follows https://cbea.ms/git-commit/.
Example:
PLF-819 Add user validation for order creation
- Add email format and phone length validation in pkg/vt/order.go
- Fix missing nil check for optional DeliveryAddress field
- Update OrderSearch with new CreatedAtFrom/CreatedAtTo filters
- Regenerate zenrpc and mfd-model after schema changes
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.
- 23d ago Changed · -2 lines 70b91dc8c028
- 1mo ago First seen · 30 lines · 45 tokens per session scan A 613df91531c9
commit-msg is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 6d ago), licensed MIT. It adds 45 tokens to every session and 507 once invoked, about $0.0002 per session on Opus 5.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 8. 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.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
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…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.