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/changelog.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/changelog)<a href="https://agentmods.dev/commands/boecht/birre/changelog"><img src="https://agentmods.dev/badge/commands/boecht/birre/changelog/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/changelog"><img src="https://agentmods.dev/badge/commands/boecht/birre/changelog.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.00757 |
| Opus 5 | $0.00006 | $0.00378 |
| Sonnet 5 | $0.00003 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
changelog 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
You will update or create a CHANGELOG.md entry that follows BiRRe standards
Rules
You MUST strictly follow the rules in edit-changelog.instructions.md Non-compliance will result in rejected entries. Pay special attention to:
- Comprehensive coverage: Analyze ALL commits on the branch (not just the latest one!)
- Category order: Changed, Added, Deprecated, Removed, Fixed, Security (EXACT order, no exceptions)
- Imperative mood: "Add feature" NOT "Added feature" or "New feature added"
- User benefits: Describe impact, not implementation details
- Headline prefixes: Use
**TOP:**for the most impactful bullets (first in Changed/Added) and**Breaking:**for any breaking behavior as mandated in the instructions file.
Inputs (from user)
- version (e.g., 4.0.0-alpha.3) — if omitted: try to extract from branch name, otherwise bump released patch version
- date (YYYY-MM-DD) — if omitted: use today
Playbook
Gather context
- Enumerate ALL commits on the current branch (= all commits since the last merge into main)
- Review EACH commit to identify user-facing changes (don't stop at the most recent commit!)
- Skim the commit messages and, if required, diffs to understand user-facing effects
Categorize
- Use the six categories in this EXACT order: Changed, Added, Deprecated, Removed, Fixed, Security
- Use imperative mood for ALL bullets (e.g., "Add X", "Fix Y", "Remove Z" — NOT "Added", "Fixed", "Removed")
- Describe user impact (not implementation): "Improve startup time" not "Refactor config loader"
- Mark breaking changes with
**Breaking:**under Changed/Removed and highlight the most significant updates with**TOP:**(always first in Changed/Added when present)
Write the entry
- Insert (or update) a section:
## [<version>] - <date>- Categories only if they have items; omit empty categories
- Keep it self-contained; avoid internal codes and commit dumps
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 · 81 lines · 13 tokens per session scan A e208c90140f9
changelog 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 757 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, 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.
ship
Ship is the operational release-prep flow for a connected project repo.
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.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.