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 Jignesh-Ponamwar/skills-mcp --skill git-commit-writergit clone --depth 1 https://github.com/Jignesh-Ponamwar/skills-mcpWrote 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/jignesh-ponamwar/skills-mcp/git-commit-writer)<a href="https://agentmods.dev/skills/jignesh-ponamwar/skills-mcp/git-commit-writer"><img src="https://agentmods.dev/badge/skills/jignesh-ponamwar/skills-mcp/git-commit-writer/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/jignesh-ponamwar/skills-mcp/git-commit-writer"><img src="https://agentmods.dev/badge/skills/jignesh-ponamwar/skills-mcp/git-commit-writer.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.00058 | $0.00975 |
| Opus 5.5 | $0.00023 | $0.00390 |
| Sonnet 5.5 | $0.00012 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
git-commit-writer 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Writer Skill
Overview
Generate precise, conventional commit messages from diffs or change descriptions. Follows the Conventional Commits 1.0.0 specification used by Angular, Vue, and thousands of open-source projects.
Conventional Commits Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types
| Type | When to use |
|---|---|
feat |
New feature visible to users |
fix |
Bug fix |
docs |
Documentation only changes |
style |
Formatting, whitespace (no logic change) |
refactor |
Code restructuring (no feature or fix) |
perf |
Performance improvement |
test |
Adding or correcting tests |
build |
Build system, dependency changes |
ci |
CI/CD configuration changes |
chore |
Other changes (e.g. updating .gitignore) |
revert |
Revert a previous commit |
Breaking Changes
Add ! after the type/scope, and a BREAKING CHANGE: footer:
feat(api)!: remove deprecated /v1/users endpoint
BREAKING CHANGE: The /v1/users endpoint has been removed. Use /v2/users instead.
Step-by-Step Process
Step 1: Understand the Change
Ask for or read the diff (git diff --staged or git diff HEAD). Understand:
- What changed (files, functions, logic)
- Why it changed (bug fix, new requirement, refactor)
- Whether it's a breaking change
Step 2: Choose the Type
Apply the type that matches the primary intent. If a PR mixes types, flag it - atomic commits are better.
Step 3: Choose the Scope (Optional)
Scope = the subsystem or module affected. Examples: (auth), (api), (ui), (db).
- Use it when the codebase has clear module boundaries
- Omit it for small or cross-cutting changes
Step 4: Write the Description
Rules:
- Imperative mood: "add feature" not "added feature" or "adds feature"
- Lowercase first letter
- No period at the end
- Max 72 characters on the first line
- Describe WHAT, not HOW
What ships with it
2 files 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.
- 1mo ago First seen · 126 lines · 58 tokens per session scan A 739623793249
git-commit-writer is a skill published in the GitHub repository Jignesh-Ponamwar/skills-mcp (10 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 975 once invoked, about $0.0002 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
dev-commit
AI DevKit · Safe git commit workflow for AI coding agents. Use when the user asks to commit, prepare a commit, stage changes, create a PR-ready checkpoint, or finish work with a conventional commit while avoiding unrelated user changes.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.
conductor-revert
Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.