Borrowing it
Nothing to install: this file belongs to tensorbee/rdocx. 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/tensorbee/rdocx/main/.claude/commands/release-notes.mdgit clone --depth 1 https://github.com/tensorbee/rdocxWrote 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/tensorbee/rdocx/release-notes)<a href="https://agentmods.dev/commands/tensorbee/rdocx/release-notes"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/release-notes/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/tensorbee/rdocx/release-notes"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/release-notes.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.00020 | $0.01353 |
| Opus 5.5 | $0.00008 | $0.00541 |
| Sonnet 5.5 | $0.00004 | $0.00271 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
release-notes 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 26d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release-notes {vX.Y.Z | rpptx-vX.Y.Z}
Prepare the human-written release record that /release publishes unchanged.
This ceremony edits only CHANGELOG.md, including the matching section and
any necessary Unreleased cleanup. It does not create a tag, push, publish, or
create a GitHub release.
Inputs
Choose exactly one complete family from the requested tag:
vX.Y.Zis the stable rdocx crates, CLI and Python distribution.rpptx-vX.Y.Zis the incubating OOXML and PowerPoint crates, CLI and Python distribution.
Historical py-* changelog sections remain readable, but no new Python-only
release tag is prepared.
Find the current sprint story assigned to the exact requested tag. Read its design plan and dependencies before collecting claims. Refuse a tag that has no release preparation story in the active sprint or whose plan is not approved.
Evidence
Build the notes from reviewed repository evidence, not memory:
- Find the previous tag in the selected family. Use the repository root when the family has no previous tag.
- Read the release story and design plan, completed
AS_BUILT.mdentries in the selected commit range, and the reviewed commits in that range. - Inspect merged pull requests and every GitHub issue or pull request named by the release story, design plan, completed delivery records, or reviewed commits in the range. Include an unmerged pull request when its reported behavior or reference implementation landed through a hardened equivalent. Use the GitHub record for its authenticated author and user-facing purpose. Do not infer contributor identity from an unauthenticated display name or commit trailer.
- Read the current compatibility and migration contract in
CHANGELOG.md, the release plan, and the relevant HLD sections. - Separate changes for the selected family from changes for the other families. Family notes cover the selected Rust, CLI and Python surfaces together, excluding the other family and npm packages. Exclude internal workflow work unless it changes a user-visible release or compatibility promise.
- Build one contribution inventory for the selected family. For each included GitHub record, capture its URL, authenticated author handle, user-visible outcome, whether it landed directly or through a hardened equivalent, and current open or closed state. Record why any candidate belongs only to the other family. This inventory is part of the release report, not a new tracked file.
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.
- 26d ago First seen · 150 lines · 20 tokens per session scan A 5e28ae9f17c8
release-notes is a command published in the GitHub repository tensorbee/rdocx (44 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 1,353 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-10-04.
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.