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 agentmods add skills/kws-projects/react-boilerplate/generate-release-notesnpx skills add kws-projects/react-boilerplate --skill generate-release-notesgit clone --depth 1 https://github.com/kws-projects/react-boilerplateWhat 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.00044 | $0.00618 |
| Opus 5 | $0.00022 | $0.00309 |
| Sonnet 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 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.
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.
- 2d 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 2mo ago), licensed MIT. It adds 44 tokens to every session and 618 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-31.
Other skills, from other repositories
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.
fastapi-rest-of-the-owl
Use when the user hands you a task definition and wants the ENTIRE development loop run end-to-end — plan, implement, review and fix, QA the change with evidence appropriate to it, open a humanized PR, then poll CI and code review, fixing and resolving until the PR is green and clean. Does everything except merge.…
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…
codexspec:release-notes
Generate release notes from git history — maintain a Keep a Changelog CHANGELOG.md entry and emit a user-facing release body, without deciding versions or mutating git state.
fastapi-release
Use when the user wants to cut a release — bump the version, update the changelog from conventional commits, and tag. Detects where the version lives, derives the next version from the commits since the last tag, and stages the release locally; it does not push or publish unless explicitly asked.
i18n
Flutter 국제화(i18n) 가이드라인. flutterlocalizations, intl, ARB 파일 관리, RTL 레이아웃, 복수형/성별 처리, 런타임 로캘 전환.