A command that turns a range of Git commits into release notes for developers, users, or both. Git commits are saved records of code changes, and a tag is a named version reference.

Use it to compare versions, create developer changelogs or user-facing notes, and append or save the result to a file.

It removes the need to manually review every commit and rewrite the changes into separate technical and plain-language summaries.

release — Command by shdennlin

Install

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.

agentmods

npx agentmods add commands/shdennlin/agent-plugins/release

Clone the repo

git clone --depth 1 https://github.com/shdennlin/agent-plugins

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 923 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00013	$0.00923
Opus 5	$0.00006	$0.00462
Sonnet 5	$0.00003	$0.00185
Haiku 4.5	$0.00001	$0.00092

Measured yesterday against content hash d380ce8a46ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

plugins/digest/commands/release.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Command

Generate structured release notes from a range of commits, with developer-facing changelogs and user-facing narratives.

Arguments

Parse the following from $ARGUMENTS:

[from] — Start tag/ref (optional, defaults to latest tag)
[to] — End tag/ref (optional, defaults to HEAD)
--dev — Developer-facing changelog grouped by commit type
--user — User-facing plain language narrative
No flag — Both sections
--write — Append output to CHANGELOG.md
--out <file> — Write output to a custom file path
--help or -h — Show usage information and exit

Instructions

Step 1: Parse Arguments

From $ARGUMENTS, extract:

help: if --help or -h is present, show usage info below and stop. Do NOT delegate to the agent.
from: first positional argument (tag or ref, or empty)
to: second positional argument (tag or ref, or empty)
dev: whether --dev flag is present
user: whether --user flag is present
write: whether --write flag is present
out: the file path following --out, if present

Help Output

If --help or -h is present, display this and stop:

Usage: /digest:release [from] [to] [options]

Generate release notes from a commit range.

Positional arguments:
  from                  Start tag/ref (default: latest tag)
  to                    End tag/ref (default: HEAD)

Options:
  --dev                 Developer-facing changelog grouped by type
  --user                User-facing plain language narrative
  --write               Append to CHANGELOG.md
  --out <file>          Write to custom file path
  -h, --help            Show this help message

Tag range detection:
  (no args)             Latest tag → HEAD
  <from>                <from> → HEAD
  <from> <to>           <from> → <to>

Examples:
  /digest:release                         # latest tag to HEAD, both formats
  /digest:release v1.0.0                  # v1.0.0 to HEAD
  /digest:release v1.0.0 v2.0.0          # between two tags
  /digest:release --dev                   # developer changelog only
  /digest:release --user                  # user narrative only
  /digest:release --write                 # append to CHANGELOG.md
  /digest:release --out docs/release.md   # write to custom file
  /digest:release v1.0.0 --dev --write    # dev changelog, append to CHANGELOG.md

Read the full file on GitHub · 117 lines

Changes

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.

yesterday First seen · 117 lines · 13 tokens per session scan A d380ce8a46ad

Subscribe to this mod's changes

release is a command published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 923 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-08-31.

Git and workflow Productivity

release

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Release Command

Arguments

Instructions

Step 1: Parse Arguments

Help Output

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement