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 lifeinchords/claude-code-skills --skill upstream-cherry-pickgit clone --depth 1 https://github.com/lifeinchords/claude-code-skillsWrote 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/lifeinchords/claude-code-skills/upstream-cherry-pick)<a href="https://agentmods.dev/skills/lifeinchords/claude-code-skills/upstream-cherry-pick"><img src="https://agentmods.dev/badge/skills/lifeinchords/claude-code-skills/upstream-cherry-pick/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/lifeinchords/claude-code-skills/upstream-cherry-pick"><img src="https://agentmods.dev/badge/skills/lifeinchords/claude-code-skills/upstream-cherry-pick.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.00132 | $0.04332 |
| Opus 5 | $0.00066 | $0.02166 |
| Sonnet 5 | $0.00026 | $0.00866 |
| Haiku 4.5 | $0.00013 | $0.00433 |
Grade A, and why
upstream-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 9d 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 — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: Always invoke scripts with relative paths from the project root, never absolute paths. Permission rules use relative patterns -- absolute paths will not match and will trigger a prompt.
Purpose
Situations where a template repository that gets cloned or forked to start new projects. Over time, project repos accumulate improvements that could flow back to the template for other projects to inherit.
This skill guides Claude through safely identifying reusable agentic patterns in a project repo and bringing them into an upstream template repo with clear operator decisions (mode + delivery) and strict safety gates (no surprise git state changes).
Prerequisites (Dependencies + local repos)
This skill requires:
gh- GitHub CLI for repo verification and commit previewjq- JSON processor for parsing script outputsgit- Version control system for cherry-picking operationsbash- Shell for running scripts (currently supports bash; future: fish, zsh)brew- macOS package manager for installing dependencies- Standard Unix utilities (typically preinstalled):
grep,sed,awk,cut,tr,wc,head,dirname,date,cp,mkdir,file - Checksum utility for backups:
shasum(macOS) orsha256sum(Linux)
This skill also assumes:
- macOS (Linux may work but is not currently tested/supported)
- A local project repo (derived from the template, containing candidate commits)
- A local template repo (the upstream destination, with push access)
Scripts
This skill includes executable scripts in .claude/skills/upstream-cherry-pick/scripts/ that handle deterministic operations:
check-deps.sh - Verifies required tools are installed
bash .claude/skills/upstream-cherry-pick/scripts/check-deps.sh
# Returns JSON with status: ok, missing, declined, or error
# Exit codes:
# 0=aall deps present or installed successfully
# 1=missing deps and operator declined install (or brew missing)
# 2=install failed
# 3 unsupported OS (currently macOS-only installer)
# On macOS, offers to install missing deps via brew
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- CHECKLIST.md 1.1 KB
- CONFLICT_TEMPLATE.md 1.2 KB
- EXAMPLES.md 8.8 KB
- references/CONTEXT.md 16 KB
- scripts/check-deps.sh 4.2 KB runs code
- scripts/conflict-backup.sh 8.0 KB runs code
- scripts/detect-mode.sh 4.2 KB runs code
- scripts/list-commits.sh 3.6 KB runs code
- scripts/preflight-check.sh 8.0 KB runs code
- TROUBLESHOOTING.md 1.8 KB
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.
- 9d ago First seen · 454 lines · 132 tokens per session scan A d5a30f041b00
upstream-cherry-pick is a skill published in the GitHub repository lifeinchords/claude-code-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 132 tokens to every session and 4,332 once invoked, about $0.0007 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-31.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.