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.
git clone --depth 1 https://github.com/pleaseai/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/commands/pleaseai/claude-code-plugins/split)<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/split"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/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/commands/pleaseai/claude-code-plugins/split"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/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.00011 | $0.00414 |
| Opus 5 | $0.00005 | $0.00207 |
| Sonnet 5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
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 yesterday.
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.
What it actually says
Divide the current branch into a stack of smaller branches. User input: $ARGUMENTS.
Modes
gt split --by-commit(-c) — split along existing commit boundaries. Each commit becomes its own branch. Only useful on a multi-commit branch.gt split --by-file "<pathspec>"(-f) — peel off files matching the pathspec onto a new branch. Repeat-ffor multiple patterns:gt split -f "*.json" -f "*.yaml".gt split --by-hunk(-h) — interactivegit add --patch-style hunk selection.
Steps
- Run
gt lsandgit log --oneline <trunk>..so the user sees what's on the branch today. - Decide the mode:
- Multiple commits already, clean per-commit grouping →
--by-commit. - Mixed files, easy to separate by path →
--by-file. - Same files but distinct concerns →
--by-hunk.
- Multiple commits already, clean per-commit grouping →
- Run
gt split <mode>. - Preserve the original branch name on one of the pieces if it already has a PR — GitHub PR branch names are immutable. Tell the user when this matters; Graphite usually prompts.
- After the split, run
gt lsand considergt submit --stackto open PRs for the new branches.
Notes
- After splitting, the auto-restack runs for everything above the split point. Resolve conflicts the usual way.
- If the user wants the opposite (combine branches), use
/graphite:fold(into parent) or/graphite:squash(commits within one branch).
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.
- yesterday First seen · 30 lines · 11 tokens per session scan A 3b9044900c2c
split is a command published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 414 once invoked, about $0.0001 per session on Opus 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-07.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.