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 jrswab/axe --skill commit-msggit clone --depth 1 https://github.com/jrswab/axeWrote 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/jrswab/axe/commit-msg)<a href="https://agentmods.dev/skills/jrswab/axe/commit-msg"><img src="https://agentmods.dev/badge/skills/jrswab/axe/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/jrswab/axe/commit-msg"><img src="https://agentmods.dev/badge/skills/jrswab/axe/commit-msg.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00227 |
| Opus 5.5 | $0.00000 | $0.00091 |
| Sonnet 5.5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00023 |
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 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 Generator
You receive a git diff of staged changes via stdin. Generate a commit message.
Format
Follow the Conventional Commits specification:
<type>(<scope>): <subject>
<body>
Types
- feat — new feature
- fix — bug fix
- refactor — code change that neither fixes a bug nor adds a feature
- docs — documentation only
- test — adding or updating tests
- chore — maintenance (deps, CI, build)
- perf — performance improvement
Rules
- Subject line: imperative mood, lowercase, no period, max 72 chars
- Scope: the package, file, or area affected (omit if too broad)
- Body: explain what and why, not how — only if the subject isn't self-explanatory
- If the diff touches multiple unrelated things, suggest splitting the commit
Output
Print only the commit message. No commentary, no markdown fences, no explanation.
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 · 35 lines · 0 tokens per session scan A 050290573818
commit-msg is a skill published in the GitHub repository jrswab/axe (897 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 227 tokens. 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
pixiv-cli-develop
Implement, diagnose, refactor, and design pixiv-cli Go changes using its actual CLI, SDK, MCP, account, and storage boundaries. Use before source changes or engineering design; choose the separate native or MCP workflow when that boundary is involved. No personal skills are required.
pr-writer
Writes a pull-request description from the actual diff.
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
gh
Patterns for invoking the GitHub CLI (gh) from agents. Covers structured output, pagination, repo targeting, search vs list, gh api fallback.
git-master
Handles git work: atomic commits, rebase, squash, blame, bisect, reflog, and history questions. Use whenever a task needs a commit or a git-history investigation; skip for ordinary code edits.