Borrowing it
Nothing to install: this file belongs to nicepkg/vsync. 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/nicepkg/vsync/main/.claude/commands/add-changelog.mdgit clone --depth 1 https://github.com/nicepkg/vsyncWrote 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/commands/nicepkg/vsync/add-changelog)<a href="https://agentmods.dev/commands/nicepkg/vsync/add-changelog"><img src="https://agentmods.dev/badge/commands/nicepkg/vsync/add-changelog/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/commands/nicepkg/vsync/add-changelog"><img src="https://agentmods.dev/badge/commands/nicepkg/vsync/add-changelog.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.00012 | $0.00564 |
| Opus 5.5 | $0.00005 | $0.00226 |
| Sonnet 5.5 | $0.00002 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
add-changelog 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
Add Changelog Entry
Generate and maintain project changelog: $ARGUMENTS
Current State
- Existing changelog: @CHANGELOG.md (if exists)
- Recent commits: !
git log --oneline -10 - Current version: !
git describe --tags --abbrev=0 2>/dev/null || echo "No tags found" - Package version: @package.json (if exists)
Task
-
Changelog Format (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.0.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 - Soon-to-be removed features ### Removed - Removed features ### Fixed - Bug fixes ### Security - Security improvements -
Version Entries
## [1.2.3] - 2024-01-15 ### Added - User authentication system - Dark mode toggle - Export functionality for reports ### Fixed - Memory leak in background tasks - Timezone handling issues -
Automation Tools
# Generate changelog from git commits npm install -D conventional-changelog-cli npx conventional-changelog -p angular -i CHANGELOG.md -s # Auto-changelog npm install -D auto-changelog npx auto-changelog -
Commit Convention
# Conventional commits for auto-generation feat: add user authentication fix: resolve memory leak in tasks docs: update API documentation style: format code with prettier refactor: reorganize user service test: add unit tests for auth chore: update dependencies -
Integration with Releases
- Update changelog before each release
- Include in release notes
- Link to GitHub releases
- Tag versions consistently
Remember to keep entries clear, categorized, and focused on user-facing changes.
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 · 91 lines · 0 tokens per session scan A 79c2993a1850
add-changelog is a command published in the GitHub repository nicepkg/vsync (61 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 564 once invoked, about $0.0000 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-30.
Other commands, from other repositories
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
cg-oss-git-hygiene
Set up an open source repository for healthy long-term maintenance — branch protection, commit signing, tag immutability, issue and PR templates, CODEOWNERS, CONTRIBUTING.md, SECURITY.md, Dependabot, stale bot, and triage workflow. Use when the user is publishing an open source project, mentions branch protection…
cg-mac-release
Build, sign, notarize, and publish a macOS app as a GitHub release with a professional DMG.
dejavu-what-shipped
Print the last N CHANGELOG release headlines for a repo — passive context priming (v0.8.4).
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
deploy
Deploy application with pre/post-deploy checks.