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.
git clone --depth 1 https://github.com/scarrillo/releaseWrote 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/scarrillo/release/changelog)<a href="https://agentmods.dev/commands/scarrillo/release/changelog"><img src="https://agentmods.dev/badge/commands/scarrillo/release/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/scarrillo/release/changelog"><img src="https://agentmods.dev/badge/commands/scarrillo/release/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.00011 | $0.02283 |
| Opus 5.5 | $0.00004 | $0.00913 |
| Sonnet 5.5 | $0.00002 | $0.00457 |
| Haiku 4.5 | $0.00001 | $0.00228 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generator
Generate a comprehensive changelog document based on recent changes in this project.
Model Selection
Before generating the changelog, check for model preference:
-
Check config for
release-plugin.modelsetting -
If not set, ask the user: "Which model should I use for changelog generation?"
- Current model (inherit from conversation)
- Claude Opus 4.5 (
claude-opus-4-5-20251101) - Most capable - Claude Sonnet 4 (
claude-sonnet-4-20250514) - Balanced (Recommended) - Claude Haiku 3.5 (
claude-3-5-haiku-20241022) - Fastest
Then ask: "Save this as default for this project?"
- If yes, persist to
.claude/config.jsonunderrelease-plugin.model
Note: Model selection applies to all plugin commands (changelog, decisions, whattotest).
Instructions
-
Analyze recent changes using this priority order:
Primary source - Current session:
- Review all work completed in this conversation session
- Include files created, modified, features implemented, and bugs fixed
- This is the most accurate and detailed source of recent work
Cross-reference with git to deduplicate:
- Check recent git commit history (
git log) - Check staged changes (
git diff --staged) - Check unstaged changes (
git diff) - Use git data to verify session work and avoid duplicate entries
- If work from the session has already been committed, use the commit info to enrich the changelog entry (commit hash, timestamp)
Handle uncommitted session work:
- If session work is not yet committed, ask the user:
- "Commit first" - Let the user commit their changes, then proceed
- "Include uncommitted" - Generate changelog including uncommitted session work
- "Skip uncommitted" - Only include work that has been committed
Reference existing changelogs:
- Check any existing changelog files for format consistency and to avoid re-documenting old changes
-
Categorize changes into:
- Features: New functionality added
- Improvements: Enhancements to existing features
- Bug Fixes: Issues that were resolved
- Breaking Changes: Changes that may affect existing functionality (if any)
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 · 258 lines · 11 tokens per session scan A ea34edd78f9b
changelog is a command published in the GitHub repository scarrillo/release (9 stars, last pushed 13d ago), licensed MIT. It adds 11 tokens to every session and 2,283 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-31.
Other commands, from other repositories
release
Cut a release — promote changelog, synthesize notes, tag, and optionally publish.
changelog
Add a changelog entry or promote unreleased changes into a version.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
ia-changelog
Create engaging changelogs for recent merges to main branch.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
gh-release
Create a new release for the marketplace or a specific plugin.