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/ShaheerKhawaja/ProductionOSWrote 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/shaheerkhawaja/productionos/ship)<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/ship"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/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/shaheerkhawaja/productionos/ship"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/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.00031 | $0.00512 |
| Opus 5 | $0.00015 | $0.00256 |
| Sonnet 5 | $0.00006 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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 8d 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 Workflow
Merge base, test, review, version, changelog, commit, push, PR. One command to ship.
Step 0: Preamble
Run templates/PREAMBLE.md. Detect base branch.
Step 1: Merge Base Branch
git fetch origin
git merge origin/$(git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@') --no-edit
If conflicts: resolve or abort and report.
Step 2: Run Tests
bun test 2>&1 || npm test 2>&1 || pytest 2>&1
If tests fail: STOP. Do not ship broken code. Report failures.
Step 3: Review Diff
Run /review on the current branch diff. If CRITICAL issues found: STOP and report.
Step 4: Bump VERSION
Auto-detect bump type from commit messages:
feat:→ minorfix:→ patchBREAKING→ major- Override with $ARGUMENTS.version_bump
Update VERSION file, package.json version, plugin.json version.
Step 5: Update CHANGELOG
Append entry with date, version, and summary of changes from git log.
Step 6: Self-Eval Gate
Run templates/SELF-EVAL-PROTOCOL.md. Score must be >= 8.0 to proceed.
Questions: Are tests passing? Is the diff clean? Are there uncommitted changes?
Step 7: Commit
git add -A
git commit -m "release: v{new_version} — {summary}"
Step 8: Push + PR
git push origin HEAD
gh pr create --title "release: v{new_version}" --body "{changelog entry}"
Guardrails
- NEVER push to main directly
- NEVER ship with failing tests
- NEVER ship with CRITICAL review findings
- Self-eval must pass before push
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.
- 8d ago First seen · 67 lines · 31 tokens per session scan A 54d762d001ed
ship is a command published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 512 once invoked, about $0.0002 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
release
Release a new version. Bumps version, updates docs/site/changelog, tags, pushes, and updates the marketplace repo.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
gh-release
Create a new release for the marketplace or a specific plugin.
release
Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
release
Invoke Eva (Release) to cut a versioned GitHub Release from main, or backfill historical releases. Routes the version-bump commit through a PR (branch protection-friendly) and uses full 40-char SHAs with gh release create to avoid the silent short-SHA rejection.