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 kensaurus/cursor-kenji --skill split-to-prsgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/split-to-prs)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/split-to-prs"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/split-to-prs/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/kensaurus/cursor-kenji/split-to-prs"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/split-to-prs.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.00045 | $0.00467 |
| Opus 5.5 | $0.00018 | $0.00187 |
| Sonnet 5.5 | $0.00009 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
split-to-prs 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
91% identical to split-to-prs — 12 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.
What it actually says
Split to PRs
Turn one pile of work into a few small PRs.
Hard rules
- Do not create branches, commit, push, or open PRs until the user approves the split plan.
- Never discard user work. No destructive git commands (
reset --hard,clean -fdx, branch deletion, force-push, history rewrite) without explicit approval. - Always save a recoverable snapshot before moving work around. This often starts from dirty work on
main, so do not assume there is already a safe branch. - Stage only named files or hunks. No
git add ./git add -A.
1. Check the state
Compare the current work to the repo's default branch, including committed and uncommitted changes. Summarize the real slices you see, and use the chat history to recover intent.
2. Propose the split
Use judgment on detail. Usually PR titles are enough. Add a one-line scope note only when a title is unclear. Show a Mermaid diagram when there are multiple slices.
Default to independent PRs off the default branch. Stack PRs only when the dependency is real.
Ask for approval before starting.
3. Execute the split
-
If there is uncommitted work, save a recoverable snapshot without changing the working tree:
SHA=$(git stash create "pre-split") if [ -n "$SHA" ]; then git update-ref "refs/backup/pre-split-$(date +%s)" "$SHA" fi -
For each approved slice, create a branch from the right base, stage and commit only the planned files or hunks, then push and open the PR.
4. Report back
Keep it short: PR titles and URLs, plus anything left on the starting branch or working tree. Do not delete the backup ref or original branch unless the user asks.
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 · 48 lines · 45 tokens per session scan A 42cf9115b270
split-to-prs is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 29d ago), licensed MIT. It adds 45 tokens to every session and 467 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to split-to-prs, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
commit
Generate a conventional commit message for staged changes.
git-sync-workspace
Sync every git repo in a Cursor multi-root workspace to its remote default branch: discover roots, preflight each repo, fetch --all --prune, checkout default, pull --ff-only. Skips dirty or unsafe repos with a clear report. Use for "sync workspace", "update all repos", "back to main", or reset workspace repos to…
commit-changes-main
Commit directly on main/master when explicitly allowed.
address-github-pr-comments
Address review comments on the current GitHub PR.
generate-pr-description
Generate PR title and description from branch diff.
fix-issue
Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.