Borrowing it
Nothing to install: this file belongs to opensupplyhub/open-supply-hub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opensupplyhub/open-supply-hub/main/.agent/skills/release-notes/SKILL.mdgit clone --depth 1 https://github.com/opensupplyhub/open-supply-hubWrote 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/opensupplyhub/open-supply-hub/release-notes)<a href="https://agentmods.dev/skills/opensupplyhub/open-supply-hub/release-notes"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/release-notes.svg" alt="Measured on agentmods" 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.00044 | $0.00962 |
| Opus 5 | $0.00022 | $0.00481 |
| Sonnet 5 | $0.00009 | $0.00192 |
| Haiku 4.5 | $0.00004 | $0.00096 |
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 8d 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.
What it actually says
Writing Release Notes
Gathering Context
Before writing the note, run these commands in parallel to understand the full scope of changes:
git log --oneline <base-branch>..HEADgit diff <base-branch>..HEAD --statgit diff <base-branch>..HEADgit log <base-branch>..HEAD --format="%B---"
File Location
- Release notes:
doc/release/RELEASE-NOTES.md - Template:
doc/release/RELEASE-NOTES-TEMPLATE.md
New entries go at the top of the file, directly after the header block (lines 1–4).
Steps
- Read the current release notes (
doc/release/RELEASE-NOTES.md) to find the latest version number and the structure of existing entries before writing anything. - Determine the new version using semver:
- Major feature release → bump minor (e.g.
2.19.0→2.20.0) - Hotfix → bump patch (e.g.
2.18.0→2.18.1)
- Major feature release → bump minor (e.g.
- Gather changes — ask the user for, or derive from git log / PR history:
- New migrations and schema changes
- Code/API changes
- Architecture/environment changes
- Bug fixes
- New user-facing features
- Required post-deployment commands
- Write the entry following the format below.
- Make them concise - each bullet should include only the most important information, avoiding unnecessary details.
- Update the RELEASE-NOTES.md file with the new entry.
Entry Format
## Release X.Y.Z
## Introduction
- Product name: Open Supply Hub
- Release date: _Provide release date_
### Database changes
#### Migrations
- <filename>.py - <What the migration does>.
#### Schema changes
- [OSDEV-XXXX](https://opensupplyhub.atlassian.net/browse/OSDEV-XXXX) - <Describe model/table changes>.
### Code/API changes
- [OSDEV-XXXX](https://opensupplyhub.atlassian.net/browse/OSDEV-XXXX) - <Describe code or API changes>.
### Architecture/Environment changes
- [OSDEV-XXXX](https://opensupplyhub.atlassian.net/browse/OSDEV-XXXX) - <Describe infra/devops changes>.
### Bugfix
- [OSDEV-XXXX](https://opensupplyhub.atlassian.net/browse/OSDEV-XXXX) - <Describe the fix>.
### What's new
- [OSDEV-XXXX](https://opensupplyhub.atlassian.net/browse/OSDEV-XXXX) - <Describe user-facing feature or change>.
### Release instructions
- Ensure that the following commands are included in the `post_deployment` command:
- `migrate`
- `reindex_database`
---
## Writing Rules
1. **Omit empty sections.** Only include sections that have content. Hotfix releases often only have `Bugfix` and `Release instructions`.
2. **Link Jira tickets** using `[OSDEV-XXXX](https://opensupplyhub.atlassian.net/browse/OSDEV-XXXX)` format.
3. **Prefix tags** when applicable:
- `[Hotfix][OSDEV-XXXX]` — for hotfix-specific items.
- `[Follow-up][OSDEV-XXXX]` — for follow-up work from a previous release.
4. **Migration entries** use the format: `* <filename>.py - <description>.`
5. **Be detailed.** Each bullet should explain _what_ changed and _why_, including endpoint paths, model names, field names, and behavioral effects.
6. **Release instructions** always include at minimum `migrate` and `reindex_database`. Add other commands (e.g. `reindex_locations_with_approved_claim`) only when the release requires them.
7. **Release date** — use the actual date if known, otherwise leave as `*Provide release date*`.
8. **Separate releases** with a `---` divider followed by two blank lines between entries.
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.
- 8d ago First seen · 100 lines · 44 tokens per session scan A 3518d0712389
release-notes is a skill published in the GitHub repository opensupplyhub/open-supply-hub (20 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 962 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.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.