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 agentmods add commands/wangke19/gemini-ai-helpers/cherry-pick-by-patchgit clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/cherry-pick-by-patch)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/cherry-pick-by-patch"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/cherry-pick-by-patch.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.00013 | $0.00353 |
| Opus 5 | $0.00006 | $0.00177 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
cherry-pick-by-patch 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 2d 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
100% identical to cherry-pick-by-patch — 0 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
Name
git:cherry-pick-by-patch
Synopsis
/git:cherry-pick-by-patch commit_hash
Description
The /git-cherry-pick-by-patch commit_hash command cherry-picks commit with hash
commit_hash into current branch. Rather then doing git cherry-pick commit_hash,
the command streams the output of git show commit_hash to
patch -p1 --no-backup-if-mismatch, and then commit changes with commit message
from commit_hash commit.
Implementation
Pre-requisites
The commit with hash commit_hash must exist. To verify that use:
git show commit_hash
and check if exit code is zero.
Fail, if there is no commit_hash in the current repository checkout.
Cherry-pick commit_hash into current branch
- Execute command
git show commit_hash | patch -p1 --no-backup-if-mismatch
and check if exit code is zero. Fail if exit code is not zero.
-
Find files removed from local checkout by the patch command and execute
git rmfor them. -
Find files added or modified by the patch command and execute
git addfor them. -
Commit changes by
git commitcommand and use commit title and description fromcommit_hashcommit.
Arguments
- $1 (required): Commit hash (e.g.,
902409c0) of commit to cherry-pick.
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.
- 2d ago First seen · 51 lines · 13 tokens per session scan A b9f8cc4a254f
cherry-pick-by-patch is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 353 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cherry-pick-by-patch, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
yapper-commit
The /yapper-commit command generates a verbose, fully-explained Git commit message for the current change or a described change. The resulting commit message explains not just what changed, but why it changed, what problem it solves, and how the solution works — providing maximum context for future readers of the git…
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
speckit.git.initialize
Initialize a Git repository with an initial commit.
commit
智能生成 Git 提交信息并提交.
changelog
Summarize staged git changes into a concise changelog/commit message.