Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rvdbreemen/adr-kitnpx agentmods add commands/rvdbreemen/adr-kit/release-adr-kitWrote 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/rvdbreemen/adr-kit/release-adr-kit)<a href="https://agentmods.dev/commands/rvdbreemen/adr-kit/release-adr-kit"><img src="https://agentmods.dev/badge/commands/rvdbreemen/adr-kit/release-adr-kit.svg" alt="Measured on agentmods" 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.00000 | $0.00780 |
| Opus 5 | $0.00000 | $0.00390 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
release-adr-kit 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 7d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the adr-kit release for version $ARGUMENTS (if empty, ask which version to release).
Since ADR-042 this is one command. scripts/release.py drives every step of
docs/RELEASING.md, and docs/RELEASING.md remains the specification it
implements. Do not perform the steps by hand while the driver exists: a second
hand-run path is how the two drift apart, and every failure this decision was
written about came from a mechanical step performed by a person.
1. Open a backlog task
Search for an existing release task; create one if there is none, and set it In Progress. Record the version and why it is a major, minor or patch bump. A behaviour change a consumer can observe is a minor bump even when it is filed as a bug fix.
2. Write the release notes first
Run the driver once:
python scripts/release.py X.Y.Z
It bumps every version site through the registry, regenerates the client
adapters, and then stops, because the CHANGELOG section it created is still
a placeholder. That stop is deliberate: release-publish.yml publishes that
section verbatim as the GitHub Release body, so it has to read as the
announcement rather than as a commit log.
Write it under ## [X.Y.Z]: group under ### Added / ### Changed /
### Fixed / ### Removed, name the user-facing impact, and call out upgrade
steps and breaking changes explicitly. Keep a Changelog, no emoji.
Update README.md where this release adds, changes or removes a user-facing
capability. The version pins move themselves; what needs judgement is whether
the README still describes what ships.
3. Run it again, and keep running it
python scripts/release.py X.Y.Z
It verifies the gates, opens the pull request into main with auto-merge, waits
for the merge, checks that the tag the workflow created resolves to
origin/main, opens the sync-back pull request into dev, and advances this
machine's prepared-directory marketplace.
Safe to re-run at any point. Each phase asks the repository whether its work is
already done, so an interrupted release is resumed, not restarted. Use
--status to see what is left without changing anything, and --skip-tests
when CI is the run you are relying on.
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.
- 7d ago First seen · 78 lines · 0 tokens per session scan A 2059ca02aed7
release-adr-kit is a command published in the GitHub repository rvdbreemen/adr-kit (6 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 780 tokens. 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
changelog
Generate a changelog from commits.
moodle-bump-version
You will bump the Moodle plugin version and wire the upgrade step.
GenerateReleaseNote
Compile short, beautiful, branded PDF release notes from one or more completed stories. Pass story IDs as arguments, or run with no arguments and the agent will ask. Reads FinishQa artefacts, groups by Epic, consolidates quality gates, proposes version number from release history, and generates a compact PDF saved to…
FinishQa
Release sign-off — verifies all TC outcomes recorded, no P0/P1 defects open, drafts plain-language release notes. Transitions ADO to Done.
wrap
Session-terminus driver — one /wrap runs the whole closing ceremony in order (coordinate teardown → checkpoint if warranted → recap → close-out → changelog → BACKLOG-shipped-row sweep → build-progress memory), driving the existing organs rather than reimplementing them. Auto-runs the reversible spine; every canonical…
close-out
Close out the scope chain on a shipped slug — reconcile shipped reality into the canonical spec, retire spent plan/blueprint artefacts to a dated archive folder, record one ship line. The terminus after /execute meets done-criteria.