add-changelog

A command for creating and maintaining a project changelog, which is a human-readable record of notable software changes. It uses the Keep a Changelog structure and Semantic Versioning conventions.

In plain words
What is it for?
It helps update CHANGELOG.md, summarize recent development work, record release versions and dates, and organize changes under standard headings.
Why use it?
It removes the need to assemble release notes manually from recent commits, version tags, and package information. It also keeps entries organized by change type, such as added, fixed, or removed.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/nicepkg/vsync/add-changelog
Clone the repo
git clone --depth 1 https://github.com/nicepkg/vsync

Made for: Claude Code.

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 564 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00564
Opus 5 $0.00006 $0.00282
Sonnet 5 $0.00002 $0.00113
Haiku 4.5 $0.00001 $0.00056

Measured 2d ago against content hash 79c2993a1850, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.claude/commands/add-changelog.md · 91 lines

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

  1. 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
    
  2. 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
    
  3. 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
    
  4. 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
    
  5. 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.

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.

  1. 2d ago First seen · 91 lines · 0 tokens per session scan A 79c2993a1850

Subscribe to this mod's changes

add-changelog is a command published in the GitHub repository nicepkg/vsync (58 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 564 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.

Related

Other commands, from other repositories