Sui is a blockchain platform for running smart contracts and managing digital assets, using the Move programming language and a network of authorities to process transactions. It is intended for developers building web3 applications and on-chain assets.
Borrowing it
Nothing to install: this file belongs to MystenLabs/sui. 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/MystenLabs/sui/main/.claude/skills/cherry-pick/SKILL.mdgit clone --depth 1 https://github.com/MystenLabs/suiWrote 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/mystenlabs/sui/cherry-pick)<a href="https://agentmods.dev/skills/mystenlabs/sui/cherry-pick"><img src="https://agentmods.dev/badge/skills/mystenlabs/sui/cherry-pick.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.00030 | $0.00533 |
| Opus 5 | $0.00015 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
cherry-pick 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 6d 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.
What it actually says
Cherry-pick to Release Branch
Cherry-picks a commit from main to a release branch and creates a PR.
Usage
/cherry-pick <commit-sha> <release-version>
Example: /cherry-pick abc123 1.64
Arguments
$ARGUMENTS should contain two space-separated values:
- The commit SHA to cherry-pick
- The release version number (e.g., "1.64" or "1.65")
Instructions
Parse the arguments to extract the commit SHA and release version. If arguments are missing or unclear, ask the user for clarification.
Execute the following steps:
1. Validate the commit exists
git show --oneline --no-patch <commit-sha>
Save the commit message for use in the PR title.
2. Fetch and checkout the release branch
The release branch naming convention is releases/sui-v<version>.0-release.
git fetch origin releases/sui-v<version>.0-release
git checkout releases/sui-v<version>.0-release
3. Cherry-pick the commit
git cherry-pick <commit-sha>
If there are conflicts:
- Inform the user about the conflicts
- Help them resolve the conflicts if they want
- After resolution, run
git cherry-pick --continue
4. Create a branch for the PR
Use the naming convention cherry-pick-<short-sha>-to-<version>:
git checkout -b cherry-pick-<short-sha>-to-<version>
5. Push the branch
git push -u origin cherry-pick-<short-sha>-to-<version>
6. Create the PR
Create a PR targeting the release branch:
gh pr create --base releases/sui-v<version>.0-release \
--title "[<version>] <original-commit-message>" \
--body "## Summary
Cherry-pick of <original-pr-link-if-available> to the <version> release branch.
Original commit: <full-commit-sha>"
7. Return to main
git checkout main
8. Report the PR URL to the user
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.
- 6d ago First seen · 81 lines · 30 tokens per session scan A 7baf6511ccc3
cherry-pick is a skill published in the GitHub repository MystenLabs/sui (7,744 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 533 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
comet-safe-delivery
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下，提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.