Borrowing it
Nothing to install: this file belongs to Indemnity83/logistics. 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/Indemnity83/logistics/mc/26.2/.claude/skills/backport/SKILL.mdgit clone --depth 1 https://github.com/Indemnity83/logisticsWrote 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/indemnity83/logistics/backport)<a href="https://agentmods.dev/skills/indemnity83/logistics/backport"><img src="https://agentmods.dev/badge/skills/indemnity83/logistics/backport.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00111 | $0.11130 |
| Opus 5 | $0.00056 | $0.05565 |
| Sonnet 5 | $0.00022 | $0.02226 |
| Haiku 4.5 | $0.00011 | $0.01113 |
Grade A, and why
backport 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 3d 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 — 568 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Port commits across mc/* branches
Port already-merged commits from a source mc/* branch to one or more target mc/*
branches. Cherry-pick is the primary mechanism; conflicts are resolved by adapting
version-specific APIs while keeping behavior identical.
Direction is whatever the task needs — the most common case is backporting from the main branch down to older maintenance branches, but the same process forward-ports up (e.g. a legacy-only fix that originated on the highest affected branch) or sideways. Only the direction of API translation changes (see the cheat-sheet).
Branch roles are not hardcoded here — they advance over time (the main branch moves to the
newest MC release, e.g. mc/26.1 → mc/26.2, and older branches age out). Read the current
roles from CLAUDE.md ("Branch Strategy" / "Cross-Version Workflow"); discover the actual
branches and worktree paths with git.
Ground rules
- Sync with remote FIRST. Before scoping or cherry-picking,
git fetchand fast-forward every branch involved — the source and each target — to itsorigin/<branch>tip. The local worktrees drift behind while you work; porting onto a stale tip means the finalpushis rejected non-fast-forward and you must rebase your picks onto the moved remote anyway (git rebase --onto origin/<branch> <old-base> <branch>) — and worse, a "missing" commit may already be on the real remote tip. Do the sync up front so the base is current. Re-fetch right before pushing too, in case the remote moved again mid-port. - One target at a time: finish one target branch fully, then move to the next. When
backporting down, go newest-MC target first (e.g.
mc/26.1 → mc/1.21.11 → mc/1.21.1); adjust to the actual source/targets the task names. - Order within a branch: oldest commit → newest (so each builds on the last).
- Cherry-pick directly onto the target branch — no feature branch, no PR. This is the
sanctioned exception to branch protection for porting already-merged commits.
Except into the default branch. Its ruleset carries no bypass, so a direct push there is
refused for everyone including admins and agent sessions. A change that must go up into the
default branch needs a normal PR for that one hop; from there it ports outward as usual. Down
and sideways ports are unaffected. Discover the default branch with
git rev-parse --abbrev-ref origin/HEAD— never hardcode it. - Push when verification passes; stop when it cannot. Finish the cherry-picks, run the
verification below, then push (
git -C <worktree> push origin <branch>) — an unpushed port leaves the branches divergent, and divergence is what makes the next port conflict. Stop and hand off before pushing when the change alters in-game behaviour that the automated suites do not cover, when you had to guess at an adaptation, or when the user asked to game-test first. Say which case applies. - The
pre-pushhook runs the unit tests for anymc/*destination, so a broken port is caught before it lands. Let it run. Pre-release branches are exempt automatically (decided fromminecraft_version; see "Branch stage" below), so a push there running no checks is expected rather than a bypass. Only--no-verifywhen the commit contains no code at all, and say so. - Identical messages, not empty commits. The goal is the same commit messages on each branch. If a commit's content is already present (see "already-present detection"), skip it — do not record an empty placeholder commit (it would create duplicate changelog entries). Confirm this skip policy with the user if a commit turns out already-present.
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.
- 3d ago First seen · 568 lines · 111 tokens per session scan A 9c20368d815a
backport is a skill published in the GitHub repository Indemnity83/logistics (6 stars, last pushed 2d ago), licensed MIT. It adds 111 tokens to every session and 11,130 once invoked, about $0.0006 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-09-04.
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.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".