Borrowing it
Nothing to install: this file belongs to KhourySpecialProjects/odyssey. 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/KhourySpecialProjects/odyssey/production/.claude/commands/ship.mdgit clone --depth 1 https://github.com/KhourySpecialProjects/odysseyWrote 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/khouryspecialprojects/odyssey/ship)<a href="https://agentmods.dev/commands/khouryspecialprojects/odyssey/ship"><img src="https://agentmods.dev/badge/commands/khouryspecialprojects/odyssey/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/commands/khouryspecialprojects/odyssey/ship"><img src="https://agentmods.dev/badge/commands/khouryspecialprojects/odyssey/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.00000 | $0.00526 |
| Opus 5.5 | $0.00000 | $0.00210 |
| Sonnet 5.5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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 today.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Branch for PR
Run pre-ship checks and prepare a PR-ready summary for the current branch.
Mode: $ARGUMENTS
If no mode specified, run full checks.
Steps
1. Verify clean state
Run git status to check for uncommitted changes. If there are unstaged changes,
warn the human and ask whether to proceed or stop.
2. Run full CI
Run the same checks as /ci full:
bash scripts/ci-local.sh
If CI fails, show the failures and STOP. Do not proceed to PR preparation with failing checks. Tell the human what needs fixing.
3. Gather branch context
git log --oneline production..HEAD
git diff --stat production..HEAD
Count files changed, insertions, deletions. Identify which areas were touched (frontend components, request functions, Strapi schemas, tests, config).
4. Check for plan/spec
Look in docs/plans/ for the active plan and spec files. Extract:
- The problem statement from the spec
- Acceptance criteria and their completion status from the plan
- Any audit verdict if an audit was run
5. Generate PR summary
Present a ready-to-copy PR description:
## Summary
- [1-3 bullet points from the spec/plan]
## Changes
- [Categorized file changes: frontend, backend, tests, config]
## Acceptance Criteria
- [x] [Each criterion from the spec, checked if met]
## Test Plan
- [ ] CI passes locally (Prettier, ESLint, Jest, builds)
- [ ] [Additional test steps based on what changed]
🤖 Generated with [Claude Code](https://claude.com/claude-code)
6. Final status
Ship Check
══════════
CI: ✓ All checks passed / ✗ [failures]
Branch: [branch name] — [N] commits ahead of production
Changes: [N] files changed (+[insertions] -[deletions])
Plan: [plan file name] — [N/M] tasks complete
Audit: [verdict if exists, or "not audited"]
Ready to push: YES / NO — [reason if no]
If everything passes, tell the human: "Branch is ready. Push when you're ready." Do NOT push — the human pushes manually per project policy.
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.
- today First seen · 90 lines · 0 tokens per session scan A 37c7ea07a24a
ship is a command published in the GitHub repository KhourySpecialProjects/odyssey (7 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 526 tokens. 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-10-02.
Other commands, from other repositories
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
red-team
Stress-test a plan, strategy, PRD, or launch with a room of hostile expert personas before you commit.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
autotask
Execute development task autonomously from description to PR-ready - handles implementation, testing, and git workflow without supervision.