writing-git-commits

writing-git-commits is a skill for Claude Code, Codex from patriceckhart/zot. It costs 14 tokens per session (80 once invoked), scanned A, original, MIT.

A workflow for writing focused Git commit messages after inspecting the staged changes. A commit is a saved set of changes in Git's project history.

In plain words
What is it for?
Review staged diffs, write concise imperative subjects, document motivation or trade-offs when needed, and verify the final staged changes.
Why use it?
It keeps commits understandable and reviewable by tying the message to the actual user-visible change.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Review staged diffs, write concise imperative subjects, document motivation or trade-offs when needed, and verify the final staged changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/patriceckhart/zot/writing-git-commits
Install

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.

Any agent
npx skills add patriceckhart/zot --skill writing-git-commits
Clone the repo
git clone --depth 1 https://github.com/patriceckhart/zot

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for writing-git-commits

README.md
[![agentmods](https://agentmods.dev/badge/skills/patriceckhart/zot/writing-git-commits/github.svg)](https://agentmods.dev/skills/patriceckhart/zot/writing-git-commits)
Your own site
<a href="https://agentmods.dev/skills/patriceckhart/zot/writing-git-commits"><img src="https://agentmods.dev/badge/skills/patriceckhart/zot/writing-git-commits/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.

agentmods 80×15 button for writing-git-commits

Your own site · 80×15
<a href="https://agentmods.dev/skills/patriceckhart/zot/writing-git-commits"><img src="https://agentmods.dev/badge/skills/patriceckhart/zot/writing-git-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 80 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00080
Opus 5 $0.00007 $0.00040
Sonnet 5 $0.00003 $0.00016
Haiku 4.5 $0.00001 $0.00008

Measured 6d ago against content hash 1f12894a60e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

writing-git-commits 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 6d 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.

examples/skills/extension-fixture/skills/writing-git-commits/SKILL.md · 13 lines

What it actually says

Writing Git commits

Use this skill when preparing a commit.

  1. Inspect the staged diff and identify the user-visible change.
  2. Keep the subject concise, imperative, and specific.
  3. Explain motivation and notable trade-offs in the body when needed.
  4. Verify the final staged diff before committing.
Changes

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.

  1. 6d ago First seen · 13 lines · 14 tokens per session scan A 1f12894a60e2

Subscribe to this mod's changes

writing-git-commits is a skill published in the GitHub repository patriceckhart/zot (336 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 80 once invoked, about $0.0001 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-09-05.