Borrowing it
Nothing to install: this file belongs to Osiris-DevWorks/smart-citizen. 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/Osiris-DevWorks/smart-citizen/main/.claude/commands/SHIP_RELEASE.mdgit clone --depth 1 https://github.com/Osiris-DevWorks/smart-citizenWrote 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/osiris-devworks/smart-citizen/ship_release)<a href="https://agentmods.dev/commands/osiris-devworks/smart-citizen/ship_release"><img src="https://agentmods.dev/badge/commands/osiris-devworks/smart-citizen/ship_release/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/osiris-devworks/smart-citizen/ship_release"><img src="https://agentmods.dev/badge/commands/osiris-devworks/smart-citizen/ship_release.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.00034 | $0.01813 |
| Opus 5.5 | $0.00014 | $0.00725 |
| Sonnet 5.5 | $0.00007 | $0.00363 |
| Haiku 4.5 | $0.00003 | $0.00181 |
Grade A, and why
SHIP_RELEASE 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship_release
Walk the release-ship sequence with checkpoints between each step. Several steps are destructive (merge to main, tag, push) or have external side effects (publish GitHub release) — confirm before each.
Run after /pre_release returns a clean verdict. This command performs the merge-to-main handoff, builds the installer, publishes the GitHub release, and offers to open the next integration branch.
Work through every step in order. After each step, stop at the CHECKPOINT and wait for the user before continuing.
Preflight
This command ships whichever release/X.Y.Z branch the user is currently on — the branch is the input. If multiple release branches exist, the user is responsible for being on the right one before invoking. Don't try to disambiguate.
Stop on the first failure.
- On a release branch:
git branch --show-currentmust matchrelease/X\.Y\.Z. ExtractX.Y.Zfor use below — this is the version we're shipping. Abort otherwise: "Switch to the release branch you want to ship before running /ship_release." - Surface other open release branches (advisory): list any other
release/*branches that exist locally or on origin. If found, print: "Other release branches exist: . Shippingrelease/X.Y.Zbased on current branch — confirm this is the one you mean." Wait for explicit confirmation before continuing the preflight. - Clean working tree:
git status --porcelainmust be empty. Abort and list offending files otherwise. - VERSION.TXT matches branch: read
VERSION.TXT, strip whitespace, confirm it equalsX.Y.Z. Abort with the mismatch otherwise. - Up to date with origin (best-effort):
git fetch origin release/X.Y.Z; ifgit rev-list --count release/X.Y.Z..origin/release/X.Y.Z> 0, abort: "Local release branch is behind origin. Pull before shipping." Skip silently if fetch fails (offline). - Pre-release was run recently (advisory only): grep recent shell history or commit log for
/pre_release; if no signal, remind the user: "Heads-up:/pre_releasedoesn't appear to have run on this branch in the recent session. The ship sequence assumes it passed. Continue?" Don't block.
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 · 133 lines · 34 tokens per session scan A c6dd4fb65ab4
SHIP_RELEASE is a command published in the GitHub repository Osiris-DevWorks/smart-citizen (114 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 1,813 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-30.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.