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 sourav15mukherjee/skillforge-free-skills --skill commit-message-generatorgit clone --depth 1 https://github.com/sourav15mukherjee/skillforge-free-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/skills/sourav15mukherjee/skillforge-free-skills/commit-message-generator)<a href="https://agentmods.dev/skills/sourav15mukherjee/skillforge-free-skills/commit-message-generator"><img src="https://agentmods.dev/badge/skills/sourav15mukherjee/skillforge-free-skills/commit-message-generator/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/sourav15mukherjee/skillforge-free-skills/commit-message-generator"><img src="https://agentmods.dev/badge/skills/sourav15mukherjee/skillforge-free-skills/commit-message-generator.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.00054 | $0.00644 |
| Opus 5 | $0.00027 | $0.00322 |
| Sonnet 5 | $0.00011 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
commit-message-generator 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 8d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Generator
Generate well-structured conventional commit messages by analyzing staged git changes.
Workflow
-
Check for staged changes Run
git diff --cached --statto see what's staged. If nothing is staged, tell the user and suggest they stage files first. -
Analyze the diff Run
git diff --cachedto get the full diff. Read through each file's changes carefully. -
Determine the commit type Based on the changes, select the appropriate type:
feat: New feature or capabilityfix: Bug fixrefactor: Code restructuring without behavior changedocs: Documentation onlytest: Adding or updating testschore: Build, CI, dependencies, toolingstyle: Formatting, whitespace, semicolonsperf: Performance improvement
-
Determine scope (optional) If the changes are localized to a specific module, component, or area, include a scope:
feat(auth): ... -
Write the subject line
- Use imperative mood: "add" not "added" or "adds"
- Keep under 72 characters
- Don't end with a period
- Be specific: "add OAuth2 Google login flow" not "update auth"
-
Write the body (if needed) For non-trivial changes, add a body separated by a blank line:
- Explain WHY, not what (the diff shows what)
- Wrap at 72 characters
- Use bullet points for multiple reasons
-
Check for breaking changes If the change breaks backward compatibility, add:
BREAKING CHANGE: description of what breaks and migration path -
Present the commit message Show the full message to the user and ask for confirmation before committing.
Rules
- Never skip the diff analysis — always base the message on actual changes
- If changes span multiple unrelated concerns, suggest splitting into separate commits
- Always use imperative mood in the subject
- Subject line must be under 72 characters
- Use a HEREDOC for the commit command to preserve formatting
- Include Co-Authored-By if the user requests it
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 83 lines · 54 tokens per session scan A a19a3ac8c2ec
commit-message-generator is a skill published in the GitHub repository sourav15mukherjee/skillforge-free-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 644 once invoked, about $0.0003 per session on Opus 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…