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 lc-rezende/AI-Custom-Skills --skill git-commit-helpergit clone --depth 1 https://github.com/lc-rezende/AI-Custom-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/lc-rezende/ai-custom-skills/git-commit-helper)<a href="https://agentmods.dev/skills/lc-rezende/ai-custom-skills/git-commit-helper"><img src="https://agentmods.dev/badge/skills/lc-rezende/ai-custom-skills/git-commit-helper.svg" alt="Measured on agentmods" 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.00036 | $0.00482 |
| Opus 5 | $0.00018 | $0.00241 |
| Sonnet 5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
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 7d 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
Git Commit Helper (No Scope)
Generate conventional commit messages without a scope.
When to use this skill
- The user asks for a commit message
- Staged changes exist
- The user is about to run
git commit - The user mentions conventional or semantic commits
Workflow
- Review staged files and the staged diff.
- Identify the primary change type and any breaking changes.
- Draft a commit message using the format below.
- Provide a short rationale and ask if the user wants adjustments.
Commit format (no scope)
<type>: <subject>
<body>
<footer>
Types
feat: New featurefix: Bug fixdocs: Documentation changesstyle: Formatting only (no logic change)refactor: Code restructuring without behavior changeperf: Performance improvementstest: Test additions or fixesbuild: Build system or tooling changesci: CI/CD pipeline changeschore: Maintenance tasks
Subject checklist
- Imperative mood ("add", "fix", "update")
- 50-72 characters max
- No trailing period
- Describes what and why, not how
- Lowercase after the type
Breaking changes
If the change is breaking, include a footer:
BREAKING CHANGE: <what changed and how to migrate>
Examples
Feature
feat: add jwt authentication for api requests
- implement token validation middleware
- add login and refresh endpoints
Closes #42
Fix
fix: prevent memory leak in user list
Clean up subscriptions when the component unmounts.
Refactor
refactor: extract repository layer for database access
No functional changes. Improves testability and separation.
Breaking change
feat: update user api response structure
BREAKING CHANGE: response is now { data, metadata }.
Output expectations
- Provide the recommended commit message in full.
- Explain the chosen type and any breaking change rationale.
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.
- 7d ago First seen · 104 lines · 36 tokens per session scan A c4598d0d9d4f
git-commit-helper is a skill published in the GitHub repository lc-rezende/AI-Custom-Skills (1 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 482 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
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
git-commit
Create well-structured git commits using the Conventional Commits specification. Use when asked to "commit changes", "create a git commit", "stage and commit", "write a commit message", or "/commit". Analyzes diffs to auto-detect type and scope, generates semantic commit messages, and supports intelligent file staging.
github-pr-best-practices
Best practices for creating GitHub pull requests including conventional commits, PR formatting, and multi-language support (en/ja). Use when creating PRs, writing PR descriptions, or formatting commit messages.
git-workflow
Enhanced git operations using lazygit, gh (GitHub CLI), and delta. Triggers on: stage changes, create PR, review PR, check issues, git diff, commit interactively, GitHub operations, rebase, stash, bisect.
git-commit
Use this skill when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow.
commit
Helps write conventional commit messages, create atomic commits, and follow git best practices. Use when the agent needs to help with git commits, commit message writing, or git workflow guidance.