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/halflength-ampleness75/claude-code-recipesWrote 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/halflength-ampleness75/claude-code-recipes/commit-message)<a href="https://agentmods.dev/commands/halflength-ampleness75/claude-code-recipes/commit-message"><img src="https://agentmods.dev/badge/commands/halflength-ampleness75/claude-code-recipes/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/halflength-ampleness75/claude-code-recipes/commit-message"><img src="https://agentmods.dev/badge/commands/halflength-ampleness75/claude-code-recipes/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.00008 | $0.00698 |
| Opus 5.5 | $0.00003 | $0.00279 |
| Sonnet 5.5 | $0.00002 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a well-structured conventional commit message from the currently staged git changes.
Step 1 — Get the Staged Diff
Run git diff --cached to see what is staged. Also run git diff --cached --stat for a file summary.
If nothing is staged, inform the user: "No changes are staged. Run git add first, then invoke this command again." Then stop.
Step 2 — Determine the Commit Type
Analyze the diff to select the most appropriate type:
| Type | When to Use |
|---|---|
feat |
A new feature or user-facing capability |
fix |
A bug fix |
refactor |
Code restructuring with no behavior change |
perf |
A performance improvement |
test |
Adding or updating tests only |
docs |
Documentation-only changes |
style |
Formatting, whitespace, semicolons — no logic change |
chore |
Build scripts, CI config, dependency bumps, tooling |
ci |
CI/CD pipeline changes |
build |
Build system or external dependency changes |
revert |
Reverting a previous commit |
If the diff spans multiple types, choose the dominant one. If it is truly mixed, prefer feat > fix > refactor > chore.
Step 3 — Determine the Scope
Identify a short scope in parentheses that indicates the area of the codebase:
- Module or package name:
feat(auth):,fix(payments): - Component name:
refactor(Button): - Layer:
test(api):,docs(readme):
Omit the scope only if the change is truly project-wide.
Step 4 — Write the Subject Line
Format: type(scope): imperative description
Rules:
- Use imperative mood ("add", not "added" or "adds")
- Do not capitalize the first word after the colon
- Do not end with a period
- Keep it under 72 characters
- Be specific — "fix null check" is too vague; "fix null dereference in user lookup when email is missing" is good
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 · 79 lines · 8 tokens per session scan A 5ed0f46185d2
commit-message is a command published in the GitHub repository halflength-ampleness75/claude-code-recipes (2 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 698 once invoked, about $0.0000 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
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
deploy
Deploy application with pre/post-deploy checks.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.