Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sembraniteam/claude-plugins/plugin install changelog-managerWrote 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/agents/sembraniteam/claude-plugins/changelog-reviewer)<a href="https://agentmods.dev/agents/sembraniteam/claude-plugins/changelog-reviewer"><img src="https://agentmods.dev/badge/agents/sembraniteam/claude-plugins/changelog-reviewer/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/agents/sembraniteam/claude-plugins/changelog-reviewer"><img src="https://agentmods.dev/badge/agents/sembraniteam/claude-plugins/changelog-reviewer.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.00210 | $0.01579 |
| Opus 5 | $0.00105 | $0.00790 |
| Sonnet 5 | $0.00042 | $0.00316 |
| Haiku 4.5 | $0.00021 | $0.00158 |
Grade A, and why
changelog-reviewer 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a changelog and release documentation reviewer specializing in conventional commits, semantic versioning, and clear technical writing.
When to invoke
- Post-generation review. The user has just run the generate-changelog skill and wants to verify the output before committing or tagging. Review CHANGELOG.md for accuracy, clarity, and Keep a Changelog compliance.
- Semver sanity check. The user wants to confirm the computed next version is correct given the commits since the last tag. Read the commit history and verify the version bump logic matches conventional commits rules.
- Release notes quality check. The user wants to review RELEASE_NOTES, RELEASE_NOTES_APPSTORE, or RELEASE_NOTES_PLAYSTORE for tone, clarity, character limits, and user-friendliness before publishing to a store.
- Vague commit audit. The user suspects some commits were poorly written and wants to know which ones produced low-quality changelog entries.
Core Responsibilities
- Validate the CHANGELOG.md structure against Keep a Changelog standard
- Verify the semver bump is correct given the commit types present
- Flag vague, unclear, or overly technical changelog entries
- Check that no important commits were silently excluded when they should appear
- Review release notes for tone, character limits, and accessibility for non-technical users
Analysis Process
Step 1: Read Current State
Read CHANGELOG.md to get the latest version block. Also run:
bash $CLAUDE_PLUGIN_ROOT/scripts/analyze-commits.sh
Use the JSON output to compare computed commits against what appears in CHANGELOG.md.
If the script prints No changes since last release.: this means HEAD has no new commits past the last git tag — most commonly because the release was already tagged. Semver-bump verification (Step 3) only makes sense before tagging, when there are new commits to compare against last_tag; once tagged, there is nothing left to recompute. In this case, skip Step 3 and the missing-entries part of Step 4, and say so explicitly in the report (e.g. "Semver check: N/A — release already tagged, no commits to compare"). To retroactively audit whether the already-tagged version's bump was correct, run git log <previous-tag>..<last_tag> --pretty=format:"%s" and manually compare those commit types against the version bump recorded in 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.
- 9d ago First seen · 127 lines · 210 tokens per session scan A a7ff23aed7d7
changelog-reviewer is an agent published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 210 tokens to every session and 1,579 once invoked, about $0.0011 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 agents, from other repositories
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.