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 sembraniteam/claude-plugins --skill generate-commitgit clone --depth 1 https://github.com/sembraniteam/claude-pluginsWrote 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/sembraniteam/claude-plugins/generate-commit)<a href="https://agentmods.dev/skills/sembraniteam/claude-plugins/generate-commit"><img src="https://agentmods.dev/badge/skills/sembraniteam/claude-plugins/generate-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/sembraniteam/claude-plugins/generate-commit"><img src="https://agentmods.dev/badge/skills/sembraniteam/claude-plugins/generate-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.00140 | $0.01686 |
| Opus 5.5 | $0.00056 | $0.00674 |
| Sonnet 5.5 | $0.00028 | $0.00337 |
| Haiku 4.5 | $0.00014 | $0.00169 |
Grade A, and why
generate-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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Commit Message
Generate a conventional commit message by analyzing the current git context. Gather user intent first, then analyze and generate, and execute confirmed actions.
Pre-flight Questions
Before running any git commands, collect user intent using AskUserQuestion in up to two rounds.
Round 1 — ask both questions in a single call:
- New branch: "Do you want to create a new branch for this commit?" (Yes / No)
- Stage files: "Which files should be staged before committing?"
- If files were provided as arguments: Yes — all / Yes — provided files / No
- If no files were provided: Yes — all / No (user can select "Other" to specify custom paths)
Round 2 — ask only the questions whose condition is met; skip entirely if neither applies:
| Question | Condition | Options |
|---|---|---|
"Should this skill run git checkout -b <branch> automatically?" |
New branch = Yes | Yes / No |
"Should this skill run git commit automatically after generating the message?" |
No condition — always ask | Yes / No |
After all answers, display a confirmation to the user (substitute actual selections from user answers):
Your selections:
- New branch: Yes / No
- Stage files: Yes (
git add <files>) / No- Checkout branch: Yes / No / N/A
- Execute commit: Yes / No
Proceed immediately to Analysis & Generation after showing the confirmation — do not wait for further input.
Analysis & Generation
Collect git context — run these commands (append -- <files> to scope diffs to user-supplied paths):
git --no-pager log --oneline -10
git --no-pager status --short
git --no-pager diff
git --no-pager diff --cached
If both diffs are empty and status shows no changes, inform the user and stop.
Determine commit fields from the diff (staged = primary signal, unstaged = secondary):
What ships with it
5 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 · 128 lines · 140 tokens per session scan A 693cea084143
generate-commit is a skill published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 140 tokens to every session and 1,686 once invoked, about $0.0006 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.