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 keep-a-changelog-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/keep-a-changelog-generator)<a href="https://agentmods.dev/skills/stanfordspezi/spezivibe/keep-a-changelog-generator"><img src="https://agentmods.dev/badge/skills/stanfordspezi/spezivibe/keep-a-changelog-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/keep-a-changelog-generator"><img src="https://agentmods.dev/badge/skills/stanfordspezi/spezivibe/keep-a-changelog-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.00025 | $0.00765 |
| Opus 5 | $0.00013 | $0.00382 |
| Sonnet 5 | $0.00005 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
keep-a-changelog-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 11d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generator
Generate changelogs from git history following Keep a Changelog format.
When to Use
Use this skill when you need to:
- Generate changelog entries for a release
- Document changes since the last version
- Maintain a project's
CHANGELOG.mdfile
Use release-notes-generator instead when you need a narrative release announcement with highlights, usage examples, and migration guidance. This skill maintains the structured CHANGELOG.md file; that one writes the story of a single release.
Changelog Format
Follow Keep a Changelog:
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- New features
### Changed
- Changes in existing functionality
### Deprecated
- Features that will be removed
### Removed
- Removed features
### Fixed
- Bug fixes
### Security
- Security fixes
Change Categories
Categorize based on commit messages and code changes:
| Category | Commit Keywords | Examples |
|---|---|---|
| Added | add, create, implement, introduce | New features, screens |
| Changed | update, change, modify, refactor, improve | API changes, enhancements |
| Deprecated | deprecate | Features to be removed |
| Removed | remove, delete, drop | Deleted features |
| Fixed | fix, resolve, correct, patch | Bug fixes |
| Security | security, vulnerability, CVE | Security patches |
Git Commands
# Recent commits
git log --oneline -20
# Commits between tags
git log v1.0.0..HEAD --oneline
# Full commit messages
git log --format="%h %s%n%b" HEAD~10..HEAD
# Commits since a date
git log --since="2026-01-01" --oneline
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.
- 11d ago First seen · 132 lines · 25 tokens per session scan A baeeb735e9f2
keep-a-changelog-generator is a skill published in the GitHub repository StanfordSpezi/SpeziVibe (24 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 765 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.
ship-pr
Ship one pull request, monitor hosted CI and review feedback, follow PR policy, and request authorization before merging and cleaning up.
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…
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.