release-notes

A command for creating release notes from a project's Git history. Git history records the changes made to source code over time.

In plain words
What is it for?
Preparing categorized changelogs when publishing a software release from Git tags.
Why use it?
It gives releases a consistent summary of changes, including breaking changes, new features, fixes, and contributors. It runs when a release tag follows a version format such as v1.2.3.

Command

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/openhands/extensions/release-notes
Clone the repo
git clone --depth 1 https://github.com/OpenHands/extensions
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 80 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.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.00080
Opus 5 $0.00022 $0.00040
Sonnet 5 $0.00009 $0.00016
Haiku 4.5 $0.00004 $0.00008

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

Security

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 2d 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.

plugins/release-notes/commands/release-notes.md · 9 lines

What it actually says

Read and follow the complete instructions in the SKILL.md file located in this skill's directory.

$ARGUMENTS

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.

  1. 2d ago First seen · 9 lines · 44 tokens per session scan A e24a2f2f3f84

Subscribe to this mod's changes

release-notes is a command published in the GitHub repository OpenHands/extensions (137 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 80 once invoked, about $0.0002 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-30.