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 mehdiozdemir/awesome-agent-skills --skill git-commit-helpergit clone --depth 1 https://github.com/mehdiozdemir/awesome-agent-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/mehdiozdemir/awesome-agent-skills/git-commit-helper)<a href="https://agentmods.dev/skills/mehdiozdemir/awesome-agent-skills/git-commit-helper"><img src="https://agentmods.dev/badge/skills/mehdiozdemir/awesome-agent-skills/git-commit-helper/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/mehdiozdemir/awesome-agent-skills/git-commit-helper"><img src="https://agentmods.dev/badge/skills/mehdiozdemir/awesome-agent-skills/git-commit-helper.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.00043 | $0.03342 |
| Opus 5 | $0.00022 | $0.01671 |
| Sonnet 5 | $0.00009 | $0.00668 |
| Haiku 4.5 | $0.00004 | $0.00334 |
Grade A, and why
git-commit-helper 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 9d 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 — 572 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Helper Skill
This skill generates clear, consistent, and informative commit messages following industry standards and best practices. Use this whenever you need to commit changes, review staged files, or ensure commit history quality.
Core Principles
1. Conventional Commits Standard
Follow the Conventional Commits specification:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
2. Atomic Commits
- Each commit should represent ONE logical change
- Changes should be self-contained and reviewable
- Avoid mixing unrelated changes
- Keep commits small and focused
3. Clear Communication
- Messages should explain WHAT changed and WHY
- Anyone reading the history should understand the change
- Use imperative mood ("Add feature" not "Added feature")
- Be specific, not vague
Commit Types
Standard Types
| Type | Description | Example |
|---|---|---|
feat |
New feature for the user | feat(auth): add OAuth2 login support |
fix |
Bug fix | fix(api): resolve null pointer in user lookup |
docs |
Documentation only | docs(readme): update installation instructions |
style |
Formatting, no code change | style(lint): apply prettier formatting |
refactor |
Code change without fix/feature | refactor(utils): extract validation helpers |
perf |
Performance improvement | perf(db): add index for user queries |
test |
Adding/updating tests | test(auth): add unit tests for login flow |
build |
Build system or dependencies | build(deps): upgrade express to v5.0 |
ci |
CI/CD configuration | ci(github): add automated testing workflow |
chore |
Other changes (no src/test) | chore(release): bump version to 2.0.0 |
revert |
Revert previous commit | revert: feat(auth): add OAuth2 login support |
Breaking Changes
Use ! after type/scope or BREAKING CHANGE: in footer:
feat(api)!: remove deprecated v1 endpoints
BREAKING CHANGE: The v1 API endpoints have been removed.
Migrate to v2 endpoints as documented in the migration guide.
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.
- 9d ago First seen · 572 lines · 43 tokens per session scan A 4b8319c1e936
git-commit-helper is a skill published in the GitHub repository mehdiozdemir/awesome-agent-skills (2 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 3,342 once invoked, about $0.0002 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…