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.
git clone --depth 1 https://github.com/fatihkan/badiWrote 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/fatihkan/badi/ship)<a href="https://agentmods.dev/commands/fatihkan/badi/ship"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/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.00000 | $0.00520 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship command. Runs the pre-flight gate, decides the version bump, assembles the changelog, and opens the PR via the release-manager agent. Nothing ships unless the gate is green.
Required Tools
- Read (diff, CHANGELOG, version files)
- Edit / Write (CHANGELOG, release notes, version bump)
- Grep / Glob (scan the change set)
- Bash (tests, lint, build, git, gh CLI)
- Agent (delegate to release-manager)
When to Use
After /qa returns SHIP, as the final step. Run this to turn verified changes into a released PR. For emergency production fixes use /hotfix; for deploy orchestration use /deploy — /ship owns the PR-level release gate.
Procedure
Step 1: Confirm Readiness
- Confirm
/qa(or equivalent) has signed off. - Check
git statusand that the change set is scoped to this release.
Step 2: Delegate to Release Manager
Launch the release-manager agent. Ask it to run the pre-flight gate and, only if fully green, assemble the release:
- Gate: tests pass, lint/typecheck clean, build succeeds, no secrets in diff, not on the default branch.
- Version: choose patch / minor / major from the actual change scope.
- Changelog: group commits by type (Features / Fixes / Breaking); write user-facing notes.
- PR: branch (if needed), commit, push, open the PR with a clear body and test plan.
Step 3: Honor the Gate
If any gate item fails, stop: report the failing check with its real output and do not ship. Do not commit or push to the default branch.
Step 4: Authorization
Commit, push, and open the PR only when the user has asked to ship (or the workflow authorizes it). Otherwise, output the exact branch/commit/PR commands for the user to run.
Step 5: Post-release
- Provide the post-release checklist (tag, deploy steps, smoke verification, what to watch).
- Provide the rollback path (how to revert this release).
Output Format
- Gate Result (each check PASS/FAIL + evidence)
- Version (bump + justification)
- Changelog (Features / Fixes / Breaking)
- PR (branch, title, body, test plan)
- Post-release & Rollback
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 · 42 lines · 0 tokens per session scan A dce22880f1a6
ship is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 520 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-09-06.
Other commands, from other repositories
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
pr
Analyze changes, detect scope issues, and create a well-structured PR.