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 mir-am/skills-agents-ai-coding --skill changelog-bump-vergit clone --depth 1 https://github.com/mir-am/skills-agents-ai-codingWrote 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/mir-am/skills-agents-ai-coding/changelog-bump-ver)<a href="https://agentmods.dev/skills/mir-am/skills-agents-ai-coding/changelog-bump-ver"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/changelog-bump-ver/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/mir-am/skills-agents-ai-coding/changelog-bump-ver"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/changelog-bump-ver.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.00030 | $0.04151 |
| Opus 5 | $0.00015 | $0.02076 |
| Sonnet 5 | $0.00006 | $0.00830 |
| Haiku 4.5 | $0.00003 | $0.00415 |
Grade A, and why
changelog-bump-ver 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 — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
- Promote
## [Unreleased]entries inCHANGELOG.mdinto a new versioned release section - Create a fresh empty
## [Unreleased]section above the new release - Preserve Keep a Changelog structure with empty
Added,Changed,Deprecated,Removed,Fixed, andSecuritysubsections, and includeMiscat the end for this repo's extended template - Determine the next version using the user's requested bump method when provided
- Otherwise infer the current bump method from existing changelog history and fall back to
minorwhen history is insufficient or unclear - Use the current system date from
date +%Fin the new release heading - Update Java Maven
pom.xmlfiles by changing only the direct<project><version>value to the next development snapshot version after the release
When to use me
Use this skill when:
- A project already has a
CHANGELOG.mdwith an## [Unreleased]section - You are cutting a new release and want to move unreleased notes into a versioned entry
- You want the skill to keep a fresh empty unreleased template ready for future work
- You want Maven project versions in
pom.xmlfiles updated to the next development snapshot after the release
Do not use this skill when:
- The repository does not have a
CHANGELOG.mdyet; usemake-changelogfirst - You want to generate release notes from commits automatically
- You want to create git tags, commits, or GitHub releases as part of the same workflow
Prerequisites
Required:
CHANGELOG.mdexists at the repository rootCHANGELOG.mdcontains exactly one## [Unreleased]section
Optional:
- One or more
pom.xmlfiles if the project uses Maven
Validation checks:
# Check changelog exists
[ -f CHANGELOG.md ]
# Check unreleased section exists exactly once
[ "$(grep -c '^## \[Unreleased\]$' CHANGELOG.md)" -eq 1 ]
# Get current release date
date +%F
Error messages:
- Missing changelog ->
"Error: CHANGELOG.md not found. Create it first before bumping a release." - Missing unreleased section ->
"Error: CHANGELOG.md does not contain a ## [Unreleased] section." - Multiple unreleased sections ->
"Error: Multiple ## [Unreleased] sections found. Normalize the changelog before running this skill." - No version can be derived ->
"Error: Could not determine the next release version from CHANGELOG.md."
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 · 472 lines · 30 tokens per session scan A 0e5895297203
changelog-bump-ver is a skill published in the GitHub repository mir-am/skills-agents-ai-coding (2 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 4,151 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
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
release-notes
Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.