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/andrewsrigom/agent-skills/write-intentional-commit-messagenpx skills add andrewsrigom/agent-skills --skill write-intentional-commit-messagegit 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/write-intentional-commit-message)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/write-intentional-commit-message"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/write-intentional-commit-message.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.00055 | $0.00808 |
| Opus 5 | $0.00028 | $0.00404 |
| Sonnet 5 | $0.00011 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
write-intentional-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 4d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Intentional Commit Message
Use this skill when the task is to name a commit well, not merely make it parse.
Scope
- choosing the right Conventional Commit type
- deciding whether the work should be one commit or several
- writing concise summaries with real intent
- deciding when to amend instead of adding another commit
- avoiding vague commit titles that hide the actual change
Routing cues
- write this commit message, pick the right conventional commit type, rename this commit, split this work into commits, amend or new commit, or review whether a commit title is misleading -> use this skill
- if the task is about installing commit hooks or enforcing commit syntax in a repo -> use
setup-conventional-commits
Default path
- Read the diff or change summary first.
- Describe the effect of the change in one sentence.
- Choose the type by the effect:
featfor a new user-facing or developer-facing capabilityfixfor a bug fixrefactorfor structural change without a net-new capabilitydocsfor documentation-only changechorefor tooling, CI, or maintenance work
- Add a scope only if it makes the message clearer.
- Keep the summary short, specific, and action-oriented.
- If the diff contains multiple unrelated effects, split the commit instead of forcing one misleading title.
When to deviate
- Use a broader type only when the repo has an explicit convention that differs from the default mapping.
- Skip scope if it adds noise or duplicates the summary.
- Keep one larger commit only when the subchanges are tightly coupled and separating them would reduce clarity.
- Amend instead of adding a follow-up commit when the new changes are still part of the same original intent.
Guardrails
- choose the type by what changed in behavior or capability, not by which files were touched
- the summary should name the real change, not the activity used to produce it
- avoid one-word summaries like
cleanuporupdates - if the commit message feels generic, the commit is probably too broad or the summary is too weak
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.
- 4d ago First seen · 94 lines · 55 tokens per session scan A 76c990d437aa
write-intentional-commit-message is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 808 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
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…
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
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…
commit
Create a signed git commit following Conventional Commits, after running /pre-commit and /changelog when appropriate.
commit
Read this skill before making git commits.
et-git
ET git workflow for preparing commits and reviewing changes. Use when checking git status or diff, filtering unrelated files, staging task-scoped changes, writing Chinese commit messages, or synchronizing with remotes using rebase instead of merge.