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 pivoshenko/pivoshenko.ai --skill git-commitgit clone --depth 1 https://github.com/pivoshenko/pivoshenko.aiWrote 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/pivoshenko/pivoshenko.ai/git-commit)<a href="https://agentmods.dev/skills/pivoshenko/pivoshenko.ai/git-commit"><img src="https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/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/pivoshenko/pivoshenko.ai/git-commit"><img src="https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/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.00149 | $0.01831 |
| Opus 5.5 | $0.00060 | $0.00732 |
| Sonnet 5.5 | $0.00030 | $0.00366 |
| Haiku 4.5 | $0.00015 | $0.00183 |
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 29d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit
Conventional commit. No confirm. No dry-run.
Flow
- Parallel:
git status+git diff --staged - Nothing staged -> stage relevant (paths >
-A). Something already staged -> commit exactly the stage; mention leftover unstaged paths, don't add them. Never.env/ creds / secrets - Parallel:
git diff --staged(if just staged) +git log --oneline -5 - Read diff -> one commit or many (see Atomic) -> write msg
- Branch linked to an issue -> add the closing trailer. Read the link with
git config --get branch.$(git branch --show-current).issue;git-issue-startrecords it there. Why -> the branch name carries no ticket id by default, so this is the only durable link between the work and the tracker - Many commits from one issue -> the trailer goes on the last one only. Why -> every commit carrying
Closes #42is noise on the issue timeline, and GitHub closes on the first merged one regardless
- Branch linked to an issue -> add the closing trailer. Read the link with
- Commit now. Many groups + already mass-staged ->
git restore --staged .to unstage (modern idiom;git reset HEADalso fine), then stage+commit per group. Loop til clean - Print hash + one-liner per commit
Atomic
Mixed concerns -> split. No mega-commit.
Group by:
- Type -
feat/fix/docs/refactor/testnever share - Scope - diff modules/pkgs = diff commits
- Logical unit - one thing per commit. Each builds + tests alone
Split signals:
-
1 unrelated area
- Behavior + format/rename mixed (format separate)
- Summary needs "and" / "also" / "+"
- Unsure -> ask user how to group
Msg Format
<header>
<footer>
header required. footer optional. No body, ever.
If the header can't carry the change, the commit isn't atomic -> split it (see Atomic). The "why" lives in the PR body, the issue, or the code comment - not here.
Header
<type>(<scope>): <short summary>
- Type:
build|chore|ci|docs|feat|fix|perf|refactor|test - Scope: optional. Affected area/module/pkg. Lowercase, kebab/short noun. One scope only - pick the dominant one, else omit
- Summary: imperative present ("add" not "added"/"adds"), lowercase, no trailing
. - Whole header ≤ 72 chars. Tighter is better; aim ≤ 50 for the summary itself
- No ticket IDs in header (go in footer). No emoji. No
[WIP]
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.
- 29d ago Changed 372e85ac5994
- 1mo ago Changed · -2 lines · +8 tokens per session e9877e674c69
- 1mo ago Changed 85bf6d9c838f
- 1mo ago Changed · -42 lines faa2d4250800
- 1mo ago Changed · +1 lines · +51 tokens per session 1a7becaba486
- 1mo ago First seen · 179 lines · 90 tokens per session scan A 917b5222689a
git-commit is a skill published in the GitHub repository pivoshenko/pivoshenko.ai (6 stars, last pushed yesterday), licensed MIT. It adds 149 tokens to every session and 1,831 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
loom-git-workflow
Git operations guidance including branching strategies, commit conventions, merge workflows, conflict resolution, and worktree management.
conventional-commit
Generer conventional commit-meldinger med Nav-relevante scopes og breaking change-format.
commit-changes
Stage, commit, and amend changes with conventional commit messages. Covers reviewing changes, selective staging, writing descriptive commit messages using HEREDOC format, and verifying commit history. Use when saving a logical unit of work to version control, creating a commit with a conventional message, amending the…
configure-git-repository
Configure a Git repository with proper .gitignore, branch strategy, commit conventions, hooks, and remote setup. Covers initial setup and common patterns for R, Node.js, and Python projects. Use when initializing version control for a new project, adding a .gitignore for a specific language or framework, setting up…
git-commit
Safely create a git commit by validating repository state, staging intended changes, scanning for secrets/conflicts, generating a Conventional Commits message (repository convention first, else an English Angular default) from the staged diff, and committing without amend.
squash-branch
Review commits in a branch, date range, or recent history; group related work into a clean linear history; and verify that the final tree is unchanged. Use when the user asks to squash commits, clean Git history, combine WIP commits, organize today's commits, or prepare a readable commit stack.