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.
git clone --depth 1 https://github.com/Amey-Thakur/AI-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/commands/amey-thakur/ai-skills/commit-message)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/commit-message"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/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/commands/amey-thakur/ai-skills/commit-message"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/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.00017 | $0.00260 |
| Opus 5.5 | $0.00007 | $0.00104 |
| Sonnet 5.5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
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
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Write a git commit message for this change:
{diff}
Rules:
- Subject line: imperative mood, under 50 characters, no trailing period
(
Add retry to upload, notAdded retryorAdds retry.). - Use a conventional-commit type prefix if the project uses them (feat, fix, refactor, docs, test, chore); otherwise a plain imperative subject.
- Blank line, then a body ONLY if the change needs explanation: wrap at 72 columns, and explain WHY (the reasoning, the context the diff cannot show), not what (the diff already shows what).
- One logical change per commit; if the diff does two unrelated things, say so and propose splitting it.
Output the message in a code block, ready to paste. No preamble.
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 · 33 lines · 17 tokens per session scan A d9caeb9594cc
commit-message is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (10 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 260 once invoked, about $0.0001 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 commands, from other repositories
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
cm
Stage working tree changes and create a Conventional Commit (no push).
cp
Stage, commit, and push the current branch following git governance rules.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
commit
Run when user calls /commit or asks to generate a commit message. Analyzes staged changes and writes a structured commit message.
summarize-changes
Summarize recent changes for standup, PR, or documentation.