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 kws-projects/react-boilerplate --skill generate-release-notesgit clone --depth 1 https://github.com/kws-projects/react-boilerplateWrote 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/kws-projects/react-boilerplate/generate-release-notes)<a href="https://agentmods.dev/skills/kws-projects/react-boilerplate/generate-release-notes"><img src="https://agentmods.dev/badge/skills/kws-projects/react-boilerplate/generate-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/kws-projects/react-boilerplate/generate-release-notes"><img src="https://agentmods.dev/badge/skills/kws-projects/react-boilerplate/generate-release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00618 |
| Opus 5.5 | $0.00018 | $0.00247 |
| Sonnet 5.5 | $0.00009 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
generate-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 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.
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
Generate Release Notes
Produce release notes from the commits/PRs merged since the last release. Group by change type, keep entries user-facing, and follow the exact template below so every release reads the same way.
Steps
- Find the range since the last release tag/version:
git fetch --tags
git log "$(git describe --tags --abbrev=0)"..HEAD --pretty=format:'%s (%h)'
- Read the version from
package.jsonand today's date. - Map Conventional Commit types to sections (omit empty sections):
feat-> Featuresfix-> Bug Fixesperf/refactor-> Improvementsdocs/chore/build/ci/test-> Maintenance- any
!/BREAKING CHANGE-> Breaking Changes (list first)
- Rewrite each line as a concise, user-facing sentence (not the raw commit). Keep the short hash in parentheses. Drop noise (merge commits, release bumps).
Template
## vX.Y.Z - YYYY-MM-DD
### Breaking Changes
- <only if any>
### Features
- <user-facing description> (<hash>)
### Bug Fixes
- <user-facing description> (<hash>)
### Improvements
- <user-facing description> (<hash>)
### Maintenance
- <user-facing description> (<hash>)
Example
Input commits:
feat(auth): add login with email and password (a1b2c3d)
feat(i18n): add Arabic translations (e4f5g6h)
fix(theme): persist dark mode across reloads (i7j8k9l)
refactor(api): simplify query client setup (m0n1o2p)
chore(deps): bump vite to 7 (q3r4s5t)
chore(release): v1.2.0 [skip ci] (u6v7w8x)
Output:
## v1.2.0 - 2026-06-01
### Features
- Log in with email and password (a1b2c3d)
- Arabic language support (e4f5g6h)
### Bug Fixes
- Dark mode now persists across page reloads (i7j8k9l)
### Improvements
- Simplified React Query client setup (m0n1o2p)
### Maintenance
- Upgraded Vite to v7 (q3r4s5t)
Note: the chore(release) bump commit is intentionally excluded.
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 · 94 lines · 44 tokens per session scan A c7ea0a8c988a
generate-release-notes is a skill published in the GitHub repository kws-projects/react-boilerplate (3 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 618 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
surface-after-care
Regelmäßiger Pflegedurchlauf für ein bereits veröffentlichtes GitHub-Repository (Stufe 1, günstig und oft wiederholbar): zuerst alle Distributionsflächen des Projekts ermitteln (npm, PyPI, Registries, Marketplaces, Stores, Website) und Änderungen später dorthin spiegeln, dann Topics setzen, Privacy-Gate, Dokumente auf…
release
Versioning and CHANGELOG: SemVer mapped from Conventional Commits, Keep a Changelog format, tagging, pre-release gates. Use when cutting a version: bumping, writing the CHANGELOG entry, or tagging.
github-repo-care
Protocol for safely creating, publishing, releasing, auditing, and maintaining GitHub repositories: check local rules and locks, create .gitignore before the first add, run privacy checks, prepare README/i18n/banner/metadata, verify release tags and GitHub releases, and update organization profiles, llms.txt files…
cut-release
Cut a clean release — bump versions across all files, update changelog, create GitHub release.
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.