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/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/fix-cherrypick-robot-pr)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/fix-cherrypick-robot-pr"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/fix-cherrypick-robot-pr/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/wangke19/gemini-ai-helpers/fix-cherrypick-robot-pr"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/fix-cherrypick-robot-pr.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.00013 | $0.02104 |
| Opus 5 | $0.00006 | $0.01052 |
| Sonnet 5 | $0.00003 | $0.00421 |
| Haiku 4.5 | $0.00001 | $0.00210 |
Grade A, and why
fix-cherrypick-robot-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 5d 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 fix-cherrypick-robot-pr — 4 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.
How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
git:fix-cherrypick-robot-pr
Synopsis
/git:fix-cherrypick-robot-pr <pr-url> [error-messages]
Description
The git:fix-cherrypick-robot-pr command replaces a cherrypick-robot PR with a clean, manually-crafted cherry-pick PR that includes fixes the robot cannot handle.
The cherrypick-robot creates automated PRs but cannot:
- Fix verification failures (JSON validation, missing annotations)
- Resolve merge conflicts
- Add context-specific fixes
- Handle edge cases requiring human judgment
- Apply repository-specific cleanup
This command helps you create a replacement PR with all necessary fixes applied.
Implementation
1. Extract Information from the Robot PR
Use gh pr view <pr-url> to extract:
- Base branch (e.g.,
release-4.19) - PR title (to extract bug ID like
OCPBUGS-65944) - All commit hashes included in the PR
- PR number for later closure
- Current PR checks/CI status
Example:
gh pr view <pr-url> --json baseRefName,title,commits,number,statusCheckRollup
2. Analyze Error Messages
Parse the provided error output to identify:
- Root causes (JSON validation, missing annotations, conflicts, etc.)
- Affected files
- Required fixes
- Fix strategy
Error sources (in priority order):
- User-provided error messages (from command arguments)
- File path if provided (e.g.,
/path/to/ci-errors.log) - CI failure URL if provided
- Automatically fetch from PR status checks
3. Discover Git Remotes and Create Branch
# Discover the upstream remote (the main repository)
# Look for a remote that's not owned by the current user
UPSTREAM_REMOTE=$(git remote -v | grep "fetch" | grep -v "$(git config user.name)" | awk '{print $1}' | head -1)
# Discover the fork remote (your fork)
FORK_REMOTE=$(git remote -v | grep "$(git config user.name).*push" | awk '{print $1}' | head -1)
# If not found, fall back to common names
UPSTREAM_REMOTE=${UPSTREAM_REMOTE:-upstream}
FORK_REMOTE=${FORK_REMOTE:-origin}
# Fetch the latest base branch
git fetch $UPSTREAM_REMOTE <base-branch>
# Create new branch following naming convention
git checkout -b cherry-pick-<issue-number>-to-<base-branch> $UPSTREAM_REMOTE/<base-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.
- 5d ago First seen · 266 lines · 13 tokens per session scan A 3dad9bc047fd
fix-cherrypick-robot-pr 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 2,104 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 fix-cherrypick-robot-pr, differing in 4 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
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.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).