Borrowing it
Nothing to install: this file belongs to Flexonze/claude-init. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Flexonze/claude-init/main/.claude/skills/generate-commit-message/SKILL.mdgit clone --depth 1 https://github.com/Flexonze/claude-initWrote 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/flexonze/claude-init/generate-commit-message)<a href="https://agentmods.dev/skills/flexonze/claude-init/generate-commit-message"><img src="https://agentmods.dev/badge/skills/flexonze/claude-init/generate-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/flexonze/claude-init/generate-commit-message"><img src="https://agentmods.dev/badge/skills/flexonze/claude-init/generate-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.00012 | $0.00279 |
| Opus 5.5 | $0.00005 | $0.00112 |
| Sonnet 5.5 | $0.00002 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
generate-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 2mo 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
Generate Commit Message
Analyze staged changes and generate a single-line commit message.
Instructions
-
Check for staged changes
- Run
git diff --cachedto see what's staged - If nothing is staged, check
git statusand suggest what to stage
- Run
-
Check project conventions
- Run
git log --oneline -10to see recent commit style - Match the existing format (conventional commits, prefixes, etc.)
- Run
-
Generate a single-line commit message
Best Practices
- 50 characters or less - keep it concise
- Imperative mood - "Add feature" not "Added feature" or "Adds feature"
- Capitalize the first letter
- No period at the end
- What and why, not how
If the project uses Conventional Commits, use the format:
type(scope): description
Types: feat, fix, docs, style, refactor, test, chore
Output
Print the commit message in a code block:
Add user authentication endpoint
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.
- 2mo ago First seen · 44 lines · 12 tokens per session scan A 980b43be1d7c
generate-commit-message is a skill published in the GitHub repository Flexonze/claude-init (10 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 279 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 skills, from other repositories
what-did-i-get-done
Summarize authored commits over a user-specified time period into a concise update.
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
commit
Commit the current work — runs the quality, consistency and passport gates, branches off main if needed, stages specific files, and writes a commit whose subject states what is now true. Pushes and opens a pull request only with --pr or when the user asks; never merges — a merge happens only when the user explicitly…
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
ln-61-repository-publisher
Commits, pushes and remotely verifies authorized repository changes; does not create releases.