Borrowing it
Nothing to install: this file belongs to boecht/birre. 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/boecht/birre/main/.github/prompts/release.prompt.mdgit clone --depth 1 https://github.com/boecht/birreWrote 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/boecht/birre/release)<a href="https://agentmods.dev/commands/boecht/birre/release"><img src="https://agentmods.dev/badge/commands/boecht/birre/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/boecht/birre/release"><img src="https://agentmods.dev/badge/commands/boecht/birre/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.00013 | $0.00542 |
| Opus 5 | $0.00006 | $0.00271 |
| Sonnet 5 | $0.00003 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
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 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.
What it actually says
Goal
Given context: you’re on a dev branch with multiple existing changes and an active PR Prepare the branch for release with minimal interaction
Inputs (from user)
- next_version (e.g., 4.0.0-alpha.3)
Playbook
Changelog up to date
- Check
CHANGELOG.mdcontains a section for<next_version>in the six-category format - If missing or style violations are obvious, state what's needed and stop
Versions bumped
- Confirm
pyproject.toml [project].versionequals<next_version> - Confirm runtime
__version__exists insrc/birre/__init__.pyand equals<next_version> - If any of the versions are missing or incorrect, mention which files need updating and stop
Run tests
- Offline:
uv run pytest --offline - Online:
uv run pytest --online-only(assumeBITSIGHT_API_KEYexported) - Online selftest:
uv run birre selftest --production - If failures occur, report and stop
Stage any updated artifacts
- If tests or tooling updated tracked files (e.g., snapshots), include them
Commit and push
- Create commit:
Bump version to v<next_version>including all staged files - Push the dev branch
Next step for user
- Instruct: Approve/merge the open PR into
main - Provide tag command to run after the merge on the main branch:
- Bash:
git tag v<next_version> && git push origin v<next_version>
- Bash:
Notes
- Use
changesto verify staged content - Use
push_filesto create the commit - Use
list_commits/get_committo report hashes - Keep responses concise: checks → actions → results
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 · 70 lines · 0 tokens per session scan A 2a0ea33fe16b
release is a command published in the GitHub repository boecht/birre (2 stars, last pushed today), licensed Unlicense. It adds 13 tokens to every session and 542 once invoked, about $0.0001 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-09-08.
Other commands, from other repositories
speckit.spex.finish
Smoke test + squash + merge/keep (land the code on main).
4-close-project
Name: 4-close-project Purpose: Apply an OpenSpec change through TDD, verify it, prepare or update the PR, and leave archive for after merge.
explore-release
This legacy command is a rename notice only. Its workflow is now rpi-explore-release.
FinishQa
Release sign-off — verifies all TC outcomes recorded, no P0/P1 defects open, drafts plain-language release notes. Transitions ADO to Done.
publish-gate
Pre-publish smoke verification — pack, install into a tmpdir, run the configured smoke command, assert expected output. Catches the "code worked locally but the published tarball is broken" class of bug.
qa-ship
Run Phase 5 QA validation, acceptance testing, and release preparation.