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 tomzx/agents --skill git-commitgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/git-commit)<a href="https://agentmods.dev/skills/tomzx/agents/git-commit"><img src="https://agentmods.dev/badge/skills/tomzx/agents/git-commit/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/tomzx/agents/git-commit"><img src="https://agentmods.dev/badge/skills/tomzx/agents/git-commit.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.00017 | $0.00487 |
| Opus 5.5 | $0.00007 | $0.00195 |
| Sonnet 5.5 | $0.00003 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
git-commit 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 22d 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 Git Commit
Generates a Conventional Commits-formatted commit message from all changes in the repository and creates the commit.
Prerequisites
gitrepository with uncommitted changes (staged or unstaged)- Working directory is the root of the repository
Steps
- Review all changes:
git diff HEAD - Draft a commit message following the format below.
- Stage and commit:
git add <files> git commit -m "<type>(<scope>): <description>"
Commit Message Format
<type>(<scope>): <short description under 72 chars>
<optional body explaining what and why, not how>
Types: feat, fix, docs, style, refactor, test, chore
Rules:
- Use imperative mood: "Add feature" not "Added feature"
- Keep subject line under 72 characters
- Separate subject from body with a blank line when a body is included
- Body explains what and why, not how
Example Usage
Scenario 1: New feature Changes add a user authentication endpoint.
Commit: feat(auth): add JWT login endpoint
Scenario 2: Bug fix with explanation Changes fix a null pointer in the order processor.
fix(orders): prevent null pointer when cart is empty
Cart can be null for guest users before session is initialized.
Scenario 3: Documentation update Changes update README with new setup instructions.
Commit: docs: update setup instructions for uv
Scenario 4: Refactor across multiple files Changes restructure the database layer without changing behavior.
Commit: refactor(db): extract connection pool into separate module
Useful Commands Reference
| Command | Description |
|---|---|
git diff HEAD |
Show all uncommitted changes |
git diff --staged |
Show only staged changes |
git add <files> |
Stage specific files |
git commit -m "<message>" |
Create a commit with a message |
git log --oneline -10 |
Show recent commits for style reference |
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.
- 22d ago Changed · -4 lines 80ff6d5a6988
- 1mo ago First seen · 75 lines · 17 tokens per session scan A 205beb5a1b1b
git-commit is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 487 once invoked, about $0.0001 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-09-03.
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 8. 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.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
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…