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 motlin/claude-code-plugins --skill split-branchgit clone --depth 1 https://github.com/motlin/claude-code-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/motlin/claude-code-plugins/split-branch)<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/split-branch"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/split-branch/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/motlin/claude-code-plugins/split-branch"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/split-branch.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.00034 | $0.00628 |
| Opus 5.5 | $0.00014 | $0.00251 |
| Sonnet 5.5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
split-branch 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 9d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Split Branch
Split the current branch into one branch per commit. Never delete, modify, or force-push the original branch or any existing branch.
Use the code:cli skill.
Base Branch and Commits
Use the base branch the user named. Otherwise, in order: the upstream tracking branch, then main or master, whichever exists. If none exists, ask.
git log --oneline --reverse <base-branch>..HEAD
With 0 commits there is nothing to split; with 1, splitting isn't useful. Say so and stop.
Branch Names
For each commit, derive a short kebab-case name (3-5 words) from its subject, using prefixes like add-, fix-, update-, remove-, refactor- where they fit. For example, "Fix null pointer in checkout" becomes fix-checkout-null-pointer.
Show the proposal:
Splitting branch `<current-branch>` into <N> branches:
- <short-sha> <commit-subject> → <semantic-branch-name>
- <short-sha> <commit-subject> → <semantic-branch-name>
...
Ask via AskUserQuestion:
- "Proceed with these names" (recommended)
- "Regenerate names"
- "Use numbered naming" (
<current-branch>-1,-2, etc.) - "Cancel"
Create the Branches
Work from oldest commit to newest. For each commit, check whether the target branch exists:
git rev-parse --verify <semantic-branch-name> 2>/dev/null
If it exists and its tip equals <commit-sha>, skip it. If it exists with a different tip, append a numeric suffix (e.g., add-user-model-2). Then:
git branch <semantic-branch-name> <base-branch>
git switch <semantic-branch-name>
git cherry-pick <commit-sha>
If a cherry-pick conflicts, tell the user which commit and branch, leave the branch conflicted, and continue with the rest. When done, return to the original branch with git switch <original-branch>.
Summary
List the preserved original branch, each new branch with its commit, skipped branches, and branches that need manual conflict resolution:
Successfully split `feature-auth` into 3 branches:
Original branch (preserved):
feature-auth (3 commits)
New single-commit branches:
✓ add-user-model: abc1234 Add user model
✓ add-login-endpoint: def5678 Add login endpoint
⊘ add-session-handling: ghi9012 Add session handling (already exists, skipped)
2 branches created, 1 skipped.
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.
- 9d ago Changed e06ab6511953
- 22d ago Changed · -62 lines bed3ec889870
- 1mo ago First seen · 140 lines · 34 tokens per session scan A 1d8598ea6de5
split-branch is a skill published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 628 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-09-19.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.