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 zerocracy/zealot --skill make-git-commitgit clone --depth 1 https://github.com/zerocracy/zealotWrote 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/zerocracy/zealot/make-git-commit)<a href="https://agentmods.dev/skills/zerocracy/zealot/make-git-commit"><img src="https://agentmods.dev/badge/skills/zerocracy/zealot/make-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/zerocracy/zealot/make-git-commit"><img src="https://agentmods.dev/badge/skills/zerocracy/zealot/make-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.00027 | $0.00486 |
| Opus 5.5 | $0.00011 | $0.00194 |
| Sonnet 5.5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
make-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 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staging
Trust staged state. Commit straight from staged state, leaving edit, lint, test, and build aside. Stage files explicitly with paths user named.
Type
Respect Conventional Commits standard. Pick type from standard set. Hold to that standard set.
Description
Write description in imperative mood, lowercase.
Use no trailing period.
Keep description under 72 characters.
Prepend ticket number with # to description.
Do this when commit ties to known issue or pull request.
Breaking
Append ! after type or scope when commit introduces incompatible change.
Add BREAKING CHANGE: footer when commit introduces incompatible change.
Body
Keep body to few short sentences. Explain motivation and visible effect. Omit body when subject says enough. Keep message free of restated diffs, file lists, and obvious summaries. Keep each commit to one related change.
Footers
Add Closes #<number> or Fixes #<number> footer only when needed.
Add it only when host needs that token to auto-close ticket on merge.
Trailers
Keep every Co-authored-by: trailer free of Claude, Anthropic, and any agent.
Leave author and committer identity as Git sets them.
Keep message free of advertising trailers, signatures, and emoji.
Keep message free of Generated with lines.
Safety
Run hooks and signing as configured unless user asked to bypass them. Confine work to one fresh local commit. Leave amend, rebase, force-push, and push aside.
Verify
Verify commit subject, body, footers, and file set after committing. Create new commit on top rather than amending when something is wrong.
Example
Input: staged src/parser.rs; ties to issue #214; user says "commit it"
git commit produces:
fix: #214 reject trailing comma in arrays
The array parser accepted a trailing comma, diverging from the
JSON grammar. Tighten the lookahead so a stray comma now fails.
Closes #214
Verified description leads with #214, stays under 72 chars,
lowercase, no trailing period; footer auto-closes the issue.
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 · 79 lines · 27 tokens per session scan A fd931f9319e7
make-git-commit is a skill published in the GitHub repository zerocracy/zealot (4 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 486 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-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 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.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.