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/document-release)<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/document-release"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/document-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/shaheerkhawaja/productionos/document-release"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/document-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.00042 | $0.00365 |
| Opus 5.5 | $0.00017 | $0.00146 |
| Sonnet 5.5 | $0.00008 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
document-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 1mo 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
/document-release — Post-Ship Documentation Update
After shipping, update all documentation to match what actually shipped.
Step 0: Preamble
Run templates/PREAMBLE.md. Read the latest git diff.
Step 1: Diff Analysis
# What changed since last release
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~10)..HEAD
git diff --stat $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~10)..HEAD
Step 2: Read Current Docs
Read ALL documentation files: README.md, ARCHITECTURE.md, CONTRIBUTING.md, CLAUDE.md, CHANGELOG.md.
Step 3: Cross-Reference
For each doc, check:
- Do counts match reality? (agent count, command count, test count)
- Do version numbers match VERSION file?
- Are new features documented?
- Are removed features cleaned up?
- Are code examples still accurate?
Step 4: Update
For each discrepancy found, update the doc with accurate information. Keep the doc's existing style and tone.
Step 5: Self-Eval
Run templates/SELF-EVAL-PROTOCOL.md. Are all docs now accurate? Did we miss any?
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.
- 1mo ago First seen · 41 lines · 42 tokens per session scan A a8ab63f7c7a2
document-release is a command published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 365 once invoked, about $0.0002 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-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.
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.
close-track
Close a completed track — run quality gate, update conductor state, commit, and optionally handle the git branch.
finishing-a-development-branch
Complete development work — verify tests, push branch, create PR.