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 agentmods add commands/robotaitai/project-bedrock/shipgit clone --depth 1 https://github.com/robotaitai/project-bedrockWrote 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/robotaitai/project-bedrock/ship)<a href="https://agentmods.dev/commands/robotaitai/project-bedrock/ship"><img src="https://agentmods.dev/badge/commands/robotaitai/project-bedrock/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 | $0.00000 | $0.00223 |
| Opus 5 | $0.00000 | $0.00112 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
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 5d 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.
What it actually says
Ship
Ship is the operational release-prep flow for a connected project repo.
Behavior
- inspect git status and current branch
- refuse to continue on detached HEAD or merge conflicts
- run detected validation commands for the repo
- run knowledge sync and compaction before commit
- stage repo-local changes
- generate or accept a concise commit message
- commit and push when possible
- optionally open a PR when requested
Safety
- use
--dry-runto preview validations, git actions, and knowledge updates - knowledge updates still run through
./agent-knowledge; the script does not convert the system into repo-local storage - if the real knowledge vault lives outside the repo, the script reports that instead of pretending to stage it
- reruns are no-op when nothing changed
Expected Script Entry Point
scripts/ship.sh --project /path/to/project
scripts/ship.sh --project /path/to/project --message "chore: ship update"
scripts/ship.sh --project /path/to/project --open-pr --dry-run
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.
- 5d ago First seen · 30 lines · 0 tokens per session scan A 2e2c4a1f6a7f
ship is a command published in the GitHub repository robotaitai/project-bedrock (45 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 223 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-08-30.
Other commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
Prepare a release by updating docs and bumping the version.
ship
Deliver the increment. Then go live with a rollback you have run.