Borrowing it
Nothing to install: this file belongs to mblua/AgentsCommander. 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/mblua/AgentsCommander/main/.claude/skills/ship/SKILL.mdgit clone --depth 1 https://github.com/mblua/AgentsCommanderWrote 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/mblua/agentscommander/ship)<a href="https://agentmods.dev/skills/mblua/agentscommander/ship"><img src="https://agentmods.dev/badge/skills/mblua/agentscommander/ship/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/mblua/agentscommander/ship"><img src="https://agentmods.dev/badge/skills/mblua/agentscommander/ship.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.00031 | $0.00671 |
| Opus 5.5 | $0.00012 | $0.00268 |
| Sonnet 5.5 | $0.00006 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
ship 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 2mo 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Branch to Main
Ship the current branch through the full merge lifecycle. Execute each step in order. If any step fails, STOP and report the issue — do not continue.
Pre-flight
- Run
rtk git statusandrtk git branch --show-currentto identify the current branch - If on
main, ABORT with: "You are already on main. Switch to a feature branch first." - Show the branch name and ask the user to confirm before proceeding
Step 1 — Commit & Push
- Run
rtk git statusto check for uncommitted changes - If there are changes:
- Run
rtk git diffandrtk git log --oneline -3to understand context and commit style - Stage relevant files (prefer specific files over
git add .) - Create a commit following the repo's commit message conventions
- Run
- Push the branch to origin:
rtk git push origin <branch>- If the remote branch doesn't exist yet, use
rtk git push -u origin <branch>
- If the remote branch doesn't exist yet, use
Step 2 — Update from origin/main
- Fetch latest:
rtk git fetch origin - Check if origin/main has new commits:
rtk git log HEAD..origin/main --oneline - If there are new commits, merge:
rtk git merge origin/main - If there are merge conflicts:
- Report the conflicting files
- STOP and ask the user to resolve them
- Do NOT continue until the user says conflicts are resolved
- If merge brought new commits, push the updated branch:
rtk git push origin <branch>
Step 3 — Merge to main
- Switch to main:
rtk git checkout main - Update local main:
rtk git merge origin/main - Merge the branch with:
rtk git merge --no-ff <branch>- The
--no-ffpreserves the branch history as a merge commit
- The
- Push main to origin:
rtk git push origin main
Step 4 — Verify & Cleanup
- Verify the merge landed on origin:
rtk git log origin/main --oneline -3- Confirm the merge commit is visible
- If NOT visible, STOP and report the issue — do not delete anything
- Only after confirming the merge is on origin/main:
- Delete local branch:
rtk git branch -d <branch> - Delete remote branch:
rtk git push origin --delete <branch>
- Delete local branch:
- Final status:
rtk git branch -ato confirm cleanup
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.
- 2mo ago First seen · 62 lines · 31 tokens per session scan A 56418d28931d
ship is a skill published in the GitHub repository mblua/AgentsCommander (12 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 671 once invoked, about $0.0001 per session on Opus 5.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
app-release
Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.
npm-release
Use when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli. Also use when npm publish fails because of duplicate versions, npm authentication, browser authentication, dist-tag propagation, tarball contents, bin entry issues, or…
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
codex-pr-body
Update the title and body of one or more pull requests.