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 2ykwang/agent-skills --skill commit-splitgit clone --depth 1 https://github.com/2ykwang/agent-skillsWrote 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/2ykwang/agent-skills/commit-split)<a href="https://agentmods.dev/skills/2ykwang/agent-skills/commit-split"><img src="https://agentmods.dev/badge/skills/2ykwang/agent-skills/commit-split/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/2ykwang/agent-skills/commit-split"><img src="https://agentmods.dev/badge/skills/2ykwang/agent-skills/commit-split.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.01536 |
| Opus 5.5 | $0.00056 | $0.00614 |
| Sonnet 5.5 | $0.00028 | $0.00307 |
| Haiku 4.5 | $0.00014 | $0.00154 |
Grade A, and why
commit-split 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.
This is a copy
100% identical to commit-split — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
commit-split
Split uncommitted changes into atomic, reviewable commits. Two things matter: the user shouldn't have to classify contexts by hand (analysis and proposal are this skill's job), and the result must be verifiable (prove not a single byte of code differs before and after the split).
Flow: read state → analyze changes → propose a plan → user confirms → execute → verify losslessness. Don't ask the user to classify anything before proposing. Analyze first, present a plan, let the user adjust it.
Step 0. Read state
git status --porcelain # change list; staged/unstaged/untracked
git branch --show-current
git log --oneline -20 # learn the commit message convention
git rev-parse HEAD # record the starting point (used for verification)
git diff HEAD | git patch-id --stable # fingerprint of the original change (used for lossless verification)
Stop on: merge/rebase in progress, or conflicted files. Report the state and halt.
Watch out for:
- Changes already staged — tell the user. The split can't preserve the existing staging, so get
agreement on "unstage everything and re-split the whole thing", then run
git restore --staged .. - Untracked files — include them in the plan table but mark them separately. If they look like build junk (logs, scratch files), suggest excluding them from the commits.
Step 1. Analyze changes
Read the full git diff HEAD and the contents of untracked files, then identify logical units. Don't group
by filename — you have to read the diff to spot "two contexts mixed in one file", and spotting that is
the whole reason this skill exists.
Grouping rules, in priority order:
- Things that break apart — a new function and its call sites, a signature change and its callers, an implementation and its tests go in one commit
- Different intent, different commit — feature / bugfix / refactor / config / docs are separate
- Different domain, different commit — unrelated modules stay apart even when the intent matches
What ships with it
3 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 · 132 lines · 140 tokens per session scan A e1fca1d5e248
commit-split is a skill published in the GitHub repository 2ykwang/agent-skills (19 stars, last pushed 2mo ago), licensed MIT. It adds 140 tokens to every session and 1,536 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to commit-split, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ship-it
A GitHub workflow for finishing an implemented issue: commit the relevant changes, push a branch, create a pull request, merge it, and close the issue. GitHub is a service for hosting code and reviewing changes, and a pull request is a proposed change for review.
commit-message-writing
Use this skill when the user explicitly asks to generate, write, draft, or create a commit message, squash commit, commit title, or merge commit message for the Shopware core repository (shopware/shopware). Supports two modes — full commit messages (title + body) for branch commits, and squash merge titles…
verification-gate
You MUST use this when work is about to be called complete, done, fixed, ready, or mergeable - before a completion claim, a merge or pull request, a branch finish, or a handoff report.
review-request
You MUST use this when a completed or partially committed implementation needs an independent code review against explicit requirements, a defined task scope, and the actual Git diff, including committed and working-tree changes.
commit-all
You MUST use this when the user asks to commit all current changes at once, via /commit-all or in words ("commit everything", "commit all changes"), without giving a commit message of their own.
agy-delegate
Delegate coding tasks to the Google Antigravity CLI (agy) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.