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 nortonx/ai-tooling-free --skill create-commit-messagegit clone --depth 1 https://github.com/nortonx/ai-tooling-freeWrote 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/nortonx/ai-tooling-free/create-commit-message)<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/create-commit-message"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/create-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/nortonx/ai-tooling-free/create-commit-message"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/create-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.00041 | $0.00376 |
| Opus 5.5 | $0.00016 | $0.00150 |
| Sonnet 5.5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
create-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
Steps
- Read staged changes:
git diff --cached - Read unstaged changes:
git diff - Read recent commits for style match:
git log --oneline -10 - If both diffs are empty, stop and say "nothing to commit".
- Read the current branch name (
git branch --show-current). If it contains an issue/ticket id, reference it per the repo convention visible ingit log.
Output format
<type>(<optional scope>): <short summary in imperative mood, max 72 chars>
<optional body: what changed and why, wrapped at 72 chars, splitted as bullet items>
Where <type> is one of: feat, fix, refactor, docs, test, chore, perf, ci
If the branch name contains an issue id (e.g. 123 in feat/123-add-login), include it the way recent commits in git log do (e.g. (#123) suffix); omit it otherwise.
Rules
- Be concise: focus on the "why", not the "what" (the diff shows the what)
- Use imperative mood: "add feature" not "added feature"
- If changes span multiple concerns, suggest splitting into separate commits
- Output only the message, ready to copy-paste
- Message should be for one commit only. Do not split into more than one commit
- If quotes are to be used, use single quotes always
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 Changed af523fc13298
- 1mo ago First seen · 35 lines · 41 tokens per session scan A 226677c1ba19
create-commit-message is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 18d ago), licensed MIT. It adds 41 tokens to every session and 376 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
pr-workflow
Pull request lifecycle: commit, codex review, sync, review, fix, status, cleanup, and PR mining. Use when user wants to commit changes, get a second-opinion code review from Codex, push changes, create a PR, check PR status, fix review comments, clean up branches after merge, or mine tribal knowledge from PR reviews.…
commit-staged
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
om-open-pr
Shared PR opener for the auto pipeline — commits the worktree, pushes, reuses an existing PR or opens a ready (non-draft) PR against the configured base branch with the unified body template, applies the full SDLC label set with rationale comments, and for issue-driven runs hands the issue back and releases the lock.…
utility-pm-changelog-curator
Draft CHANGELOG entries from git log via the pm-changelog-curator sub-agent, applying the repo hygiene rules (describe what changed, public paths only, no attribution trailers). Returns a layered draft with a status summary for maintainer review; refuses a dirty working tree unless --committed-only is passed. Use when…
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.
git-mastery
Advanced Git: rebase, bisect, reflog, cherry-pick, worktrees, LFS. Triggers: rebase, bisect, cherry-pick, reflog, force push, merge conflict, worktree.