Borrowing it
Nothing to install: this file belongs to rex/mcp-rancher. 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/rex/mcp-rancher/main/.claude/commands/ship.mdgit clone --depth 1 https://github.com/rex/mcp-rancherWrote 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/rex/mcp-rancher/ship)<a href="https://agentmods.dev/commands/rex/mcp-rancher/ship"><img src="https://agentmods.dev/badge/commands/rex/mcp-rancher/ship.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.00014 | $0.00318 |
| Opus 5 | $0.00007 | $0.00159 |
| Sonnet 5 | $0.00003 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ship — 100% identical, 0 lines differ
What it actually says
Context
- Branch: !
git branch --show-current - Status: !
git status --short - Ahead of main: !
git rev-list --count origin/main..HEAD 2>/dev/null || echo 'unknown'
Pipeline
- Spawn
test-runner— if any failures, STOP and report. - Spawn
reviewer— if verdict is REQUEST-CHANGES or BLOCK, STOP and report. - Run
make check-if-the-agent-can-consider-this-task-completed— if non-zero exit, STOP. - Update
TASK_STATE.md:- Check boxes for completed slices
- Set status to
doneif all slices are complete - Fill in §6 Handoff note
- Compose a conventional commit message from the diff (feat/fix/chore/refactor/docs/test).
- Run
git add -A && git statusand show what will be committed.
Per VIBE.yaml.workflow.default_slice_completion_behavior:
commit-push-and-pause→ commit + push, then STOP for human review.commit-push-and-continue→ commit + push, then resume the next slice.- Anything else → STOP; human commits.
Respect signed-commit policy (signed_commits_required: true).
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.
- 6d ago First seen · 32 lines · 14 tokens per session scan A ef095c1df504
ship is a command published in the GitHub repository rex/mcp-rancher (1 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 318 once invoked, about $0.0001 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 commands, from other repositories
prepare-release
Command "prepare-release" from qdhenry/Claude-Command-Suite, covering prepare release command, instructions, emergency hotfix process, make minimal fix and fast-track testing and deployment.
pr
Analyze changes, detect scope issues, and create a well-structured PR.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
double-check
Comprehensive verification with automated quality gates, confession gathering, and confidence-based issue filtering. Default: self-review with gates. --deep: multi-agent review via code-reviewer agent. Use before committing, after fixing bugs, or to validate feature completeness.
review-branch
Review an existing branch holistically before merging — blast radius, conventions, security, and spec compliance.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.