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 StanfordSpezi/SpeziVibe --skill release-notes-generatorgit clone --depth 1 https://github.com/StanfordSpezi/SpeziVibeWrote 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/stanfordspezi/spezivibe/release-notes-generator)<a href="https://agentmods.dev/skills/stanfordspezi/spezivibe/release-notes-generator"><img src="https://agentmods.dev/badge/skills/stanfordspezi/spezivibe/release-notes-generator/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/stanfordspezi/spezivibe/release-notes-generator"><img src="https://agentmods.dev/badge/skills/stanfordspezi/spezivibe/release-notes-generator.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.00021 | $0.00841 |
| Opus 5 | $0.00010 | $0.00420 |
| Sonnet 5 | $0.00004 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
release-notes-generator 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
Create release notes summarizing features, fixes, and breaking changes for releases.
When to Use
Use this skill when you need to:
- Prepare release notes for a new version
- Summarize changes for users/stakeholders
- Document migration steps for breaking changes
Use keep-a-changelog-generator instead when you need to maintain the project's CHANGELOG.md file. This skill writes the narrative announcement for a single release; that one keeps the structured, cumulative changelog.
Release Notes Structure
# Release v1.2.0
## Highlights
Brief summary of the most important changes (2-3 sentences).
## New Features
### Feature Name
Description of what it does and why it matters.
**Usage:**
```typescript
// Code example
Improvements
- Improvement 1
- Improvement 2
Bug Fixes
- Fixed issue with X (#123)
- Resolved Y when Z
Breaking Changes
Change Name
What changed: Description
Migration:
// Before
oldMethod();
// After
newMethod();
Dependencies
- Updated
package-namefrom 1.0.0 to 2.0.0
## Information Gathering
### Git Commands
```bash
# Commits since last release
git log v1.1.0..HEAD --oneline
# Detailed commit messages
git log v1.1.0..HEAD --format="%h %s%n%b%n---"
# Files changed
git diff v1.1.0..HEAD --stat
# Contributors
git log v1.1.0..HEAD --format="%an" | sort | uniq
Writing Guidelines
Highlights Section
Focus on user value:
- What can users do now that they couldn't before?
- What problems are solved?
- Why should they upgrade?
Feature Descriptions
Include:
- What it does
- Why it matters
- Basic usage example
Breaking Changes
Must include:
- Clear description of what changed
- Why it changed
- Step-by-step migration guide
- Code examples (before/after)
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.
- 9d ago First seen · 179 lines · 21 tokens per session scan A 3a4e7515ca80
release-notes-generator is a skill published in the GitHub repository StanfordSpezi/SpeziVibe (23 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 841 once invoked, about $0.0001 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
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.
memstack-development-changelog-generator
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
auto-pr
Use when the user invokes /auto-pr or asks to "open N PRs against ", "auto-contribute to ", or "raise mergeable PRs automatically". Wraps the vouch auto-pr CLI: points at any github repo, learns its contribution norms (from shipped guidance, else synthesized from merged PRs), sources work items (open issues first…
ship-pr
Ship one pull request, monitor hosted CI and review feedback, follow PR policy, and request authorization before merging and cleaning up.
release
Cut a booping plugin release — verify the version bump against the last published tag, draft public-voiced release notes, merge the release branch into master, tag, and publish the GitHub release. Use when cutting a vX.Y.Z release of this repo.