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 skilletmd/skillet --skill commit-messagegit clone --depth 1 https://github.com/skilletmd/skilletWrote 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/skilletmd/skillet/commit-message)<a href="https://agentmods.dev/skills/skilletmd/skillet/commit-message"><img src="https://agentmods.dev/badge/skills/skilletmd/skillet/commit-message/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/skilletmd/skillet/commit-message"><img src="https://agentmods.dev/badge/skills/skilletmd/skillet/commit-message.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.00042 | $0.00554 |
| Opus 5.5 | $0.00017 | $0.00222 |
| Sonnet 5.5 | $0.00008 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
commit-message 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 1mo 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
commit-message
The diff shows what changed. The commit message exists to say why — the context that isn't in the code and won't be in anyone's head in six months. This skill writes that.
When to use
Any commit worth more than git commit -m "fix". Especially before committing a change whose reason isn't obvious from the diff.
Read what you're committing
git diff --staged
Commit one logical change at a time. If the staged diff does two unrelated things, that's two commits — git restore --staged <file> to split them.
The format
<type>: <subject, imperative, under 50 chars>
<body: why this change, what it affects, wrapped at 72 chars>
Subject line:
- Imperative mood: "add", "fix", "remove" — not "added" or "fixes". It completes the sentence "If applied, this commit will ___."
- Under 50 characters. If it won't fit, the commit is probably too big.
- No trailing period.
Type (conventional commits — optional, but be consistent):
feat, fix, refactor, docs, test, chore, perf.
Body (skip it only when the subject is genuinely complete on its own):
- Explain why, not what — the diff already shows what.
- Note side effects, migrations, or anything a future reader would be surprised by.
- Reference the issue:
Closes #123.
Example
fix: stop double-charging on retried checkout
The payment client retried on a 504 without checking whether the
first request had already succeeded, charging some customers twice.
Make the charge idempotent, keyed on the order ID.
Closes #482
The diff alone would show a reviewer a new idempotency_key parameter. The message is where the why lives.
What to avoid
"fix bug","update","wip","changes"— these cost a future engineer agit blameand a guess.- Restating the diff: "changed line 42 in auth.js" — they can see that.
- Bundling unrelated changes so the subject has to list three things with "and".
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.
- 1mo ago First seen · 64 lines · 42 tokens per session scan A 2160c5c12d01
commit-message is a skill published in the GitHub repository skilletmd/skillet (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 554 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
oma-scm
Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.