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.
npx skills add OpenHands/extensions --skill release-notesgit clone --depth 1 https://github.com/OpenHands/extensionsWrote 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/skills/openhands/extensions/release-notes)<a href="https://agentmods.dev/skills/openhands/extensions/release-notes"><img src="https://agentmods.dev/badge/skills/openhands/extensions/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/skills/openhands/extensions/release-notes"><img src="https://agentmods.dev/badge/skills/openhands/extensions/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.00897 |
| Opus 5.5 | $0.00019 | $0.00359 |
| Sonnet 5.5 | $0.00010 | $0.00179 |
| Haiku 4.5 | $0.00005 | $0.00090 |
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 1mo 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.
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 \ 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 Changessection 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
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.
- .claude-plugin 7 B
- .codex-plugin 7 B
- .plugin/plugin.json 535 B
- action.yml 4.1 KB
- commands/release-notes.md 403 B
- README.md 10 KB
- scripts/agent_script.py 9.9 KB runs code
- scripts/generate_release_notes.py 24 KB runs code
- scripts/prompt.py 4.3 KB runs code
- scripts/validate_release_notes.py 11 KB runs code
- skills/release-notes 29 B
- workflows/release-notes.yml 3.0 KB
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.
- 1mo ago First seen · 93 lines · 48 tokens per session scan A bf3b595334ef
release-notes is a skill published in the GitHub repository OpenHands/extensions (167 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 897 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.