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 Notysoty/openagentskills --skill git-commit-writergit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/git-commit-writer)<a href="https://agentmods.dev/skills/notysoty/openagentskills/git-commit-writer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/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/notysoty/openagentskills/git-commit-writer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/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.00016 | $0.01220 |
| Opus 5.5 | $0.00006 | $0.00488 |
| Sonnet 5.5 | $0.00003 | $0.00244 |
| Haiku 4.5 | $0.00002 | $0.00122 |
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Writer
What this skill does
This skill directs the agent to read a git diff (or a plain description of changes) and produce a well-formed commit message following the Conventional Commits specification. It chooses the right type (feat, fix, chore, docs, refactor, test, style, perf, ci), picks an appropriate scope, writes a concise subject line, and — when the change is large enough to warrant it — adds a descriptive body.
Use this when you want consistent, meaningful commit history without having to remember the format every time.
How to use
Claude Code / Cline
Copy this file to .agents/skills/git-commit-writer/SKILL.md in your project root.
Then ask the agent:
- "Write a commit message for my staged changes using the Git Commit Writer skill."
- "Here's a diff. Use the Git Commit Writer skill to produce a commit message."
For Claude Code, you can also run git diff --staged first and paste the output into the chat.
Cursor
Add the contents of the "Prompt / Instructions" section below to your .cursorrules file, or paste it into the Cursor AI pane before asking for a commit message.
Codex
Paste the diff into the Codex chat along with the instructions from the section below. Codex works best when you include the full diff rather than a summary.
The Prompt / Instructions for the Agent
When asked to write a commit message, follow these steps:
-
Read the diff. If not provided, ask for
git diff --stagedoutput. Understand every file changed. -
Determine the commit type using these rules:
feat— a new feature or behavior visible to users or callersfix— a bug fixrefactor— code restructuring with no behavior changeperf— performance improvementtest— adding or fixing testsdocs— documentation only (README, comments, etc.)style— formatting, whitespace, lint (no logic change)chore— build scripts, dependencies, toolingci— CI/CD pipeline 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.
- 1mo ago First seen · 128 lines · 16 tokens per session scan A aec0cbb19388
Git Commit Writer is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,220 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
chinese-commit-conventions
A Chinese-language convention for writing Git commit messages, based on Conventional Commits, a standard format that tools can use to classify changes and build changelogs.
commit
Create well-formatted commits with conventional commit messages and emoji.
git-notes
Use when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides git notes commands and patterns for attaching non-invasive metadata to Git objects.
public-git-workflow-expert-base
A reference guide to Git, a tool for tracking code changes and collaborating through branches and reviews. It also documents team rules for commits, branch naming, Gitea, and repository mirroring.
git-authoring
Authors and executes git work end to end — Conventional Commits messages, pull-request content, release notes, and pull-request review, plus the repository operations an engineer runs daily: branching, rebasing, squashing, cherry-picking, reverting, merge-conflict resolution, stashes, tags, remotes, and recovery…
conventional-commits
The Conventional Commits format — also called "semantic commits" / semantic commit messages — a type(scope): description header (feat, fix, …) plus an optional BREAKING CHANGE footer, and how it makes history machine-readable to drive automated version bumps and changelogs. Use when writing a commit message or PR…