What is release-notes?

A tool that turns a range of Git commits and pull requests into release notes. Release notes are a summary of what changed between software versions.

Use it when preparing GitHub releases or changelogs from version tags, including features, fixes, breaking changes, and contributor names.

It avoids manually reviewing every change and makes release summaries more consistent and complete.

release-notes — Skill by OpenHands

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 skills/openhands/extensions/release-notes

Any agent

npx skills add OpenHands/extensions --skill release-notes

Clone the repo

git clone --depth 1 https://github.com/OpenHands/extensions

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 1 finding. 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.00048	$0.00897
Opus 5	$0.00024	$0.00449
Sonnet 5	$0.00010	$0.00179
Haiku 4.5	$0.00005	$0.00090

Measured 2d ago against content hash bf3b595334ef, 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 1 finding 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.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/agent_script.py, scripts/generate_release_notes.py, scripts/prompt.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -o .github/workflows/release-notes.yml \

plugins/release-notes/SKILL.md · 93 lines

How it starts

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

Release Notes Generator Plugin

Automates the generation of standardized release notes for OpenHands repositories using an OpenHands agent. The agent reviews the release range, judges significance, groups related PRs, and produces concise markdown for GitHub releases or changelogs.

Features

Automatic tag detection: Finds the previous release tag to determine the commit range
Agent-based editing: Lets the agent decide which changes matter, open with a short conversational summary, and group related PRs into higher-signal summaries while keeping toolkit-maintainer-only details out of the main sections unless they are unusually significant
Structured GitHub context: Supplies PR titles, labels, descriptions, and contributor metadata to guide the agent
Contributor attribution: Includes PR numbers and author usernames for each change
Attribution validation: Verifies every change bullet contains explicit PR/commit references and the matching author handles
Full coverage appendix: Appends a compact ### 🔎 Small Fixes/Internal Changes section grouped by author when needed so every PR and author in the release range is still listed somewhere in the final markdown
New contributor highlighting: Identifies first-time human contributors from merged PR history and excludes bot accounts
Flexible output: Can update GitHub release notes or generate CHANGELOG.md entries

Quick Start

As a GitHub Action

Copy the workflow file to your repository:

mkdir -p .github/workflows
curl -o .github/workflows/release-notes.yml \
  https://raw.githubusercontent.com/OpenHands/extensions/main/plugins/release-notes/workflows/release-notes.yml

PowerShell equivalent:

New-Item -ItemType Directory -Force .github\workflows | Out-Null
Invoke-WebRequest `
  -Uri https://raw.githubusercontent.com/OpenHands/extensions/main/plugins/release-notes/workflows/release-notes.yml `
  -OutFile .github\workflows\release-notes.yml

Read the full file on GitHub · 93 lines

Files

What ships with it

12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago First seen · 93 lines · 48 tokens per session scan A bf3b595334ef

Subscribe to this mod's changes

release-notes is a skill published in the GitHub repository OpenHands/extensions (137 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 897 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Productivity

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

release-notes