Borrowing it
Nothing to install: this file belongs to swarm-ai-research/swarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/swarm-ai-research/swarm/main/.claude/commands/cherry_pick_pr.mdgit clone --depth 1 https://github.com/swarm-ai-research/swarmWrote 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/swarm-ai-research/swarm/cherry_pick_pr)<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/cherry_pick_pr"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/cherry_pick_pr.svg" alt="Measured on agentmods" 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.00000 | $0.00626 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
cherry_pick_pr 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 8d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cherry_pick_pr
Cherry-pick one or more commits onto a new branch from main and open a PR. Useful when a commit landed on the wrong branch or you want to split a multi-commit branch into separate PRs.
Usage
/cherry_pick_pr <commit-sha> [commit-sha...] [branch-name]
Examples:
/cherry_pick_pr abc1234(cherry-pick one commit, auto-generate branch name)/cherry_pick_pr abc1234 def5678 fix/gastown-bugs(cherry-pick two commits onto a named branch)
Behavior
-
Validate inputs:
- Verify each commit SHA exists:
git cat-file -t <sha>. - If any SHA is invalid, abort with an error.
- Show the commit messages for confirmation:
git log --oneline -1 <sha>for each.
- Verify each commit SHA exists:
-
Create a clean branch from main:
git fetch origin maingit checkout -b <branch-name> origin/main- If no branch name provided, derive one from the first commit's message (e.g.
fix/circuit-breaker-reset).
-
Cherry-pick commits:
- For each SHA in order:
git cherry-pick <sha> --no-commit, thengit commit --no-verifywith the original message plusCo-Authored-By: Claude Opus 4.6 <[email protected]>. - If a cherry-pick has conflicts, stop and report the conflicts. Do not auto-resolve.
- For each SHA in order:
-
Push and open PR:
git push -u origin <branch-name>gh pr create --head <branch-name> --base main --title "..." --body "..."- Title: derived from commit message(s). If multiple commits, summarize.
- Body format:
## Summary(bullet points from each commit),## Test plan, Claude Code footer.
-
Clean up source branch (optional):
- If the commits came from a feature branch (not main), ask the user if they want to remove those commits from the source branch.
- If yes:
git checkout <source-branch> && git rebase --onto <sha>~1 <sha> <source-branch>(for single commit) or interactive rebase guidance for multiple. - If no: leave the source branch as-is.
- Never force-push the source branch without explicit confirmation.
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.
- 8d ago First seen · 51 lines · 0 tokens per session scan A 6b25690ffa88
cherry_pick_pr is a command published in the GitHub repository swarm-ai-research/swarm (41 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 626 tokens. 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-30.
Other commands, from other repositories
eval-merge
Use the Read tool to load .skill-compass/{skill-name}/manifest.json. Verify.
speckit.git.feature
Create a feature branch with sequential or timestamp numbering.
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
speckit.git.initialize
Initialize a Git repository with an initial commit.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
speckit.git.remote
Detect Git remote URL for GitHub integration.