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 phuonghx/aim-cli --skill changelog-releasegit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/changelog-release)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/changelog-release"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/changelog-release/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/phuonghx/aim-cli/changelog-release"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/changelog-release.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.00084 | $0.01393 |
| Opus 5.5 | $0.00034 | $0.00557 |
| Sonnet 5.5 | $0.00017 | $0.00279 |
| Haiku 4.5 | $0.00008 | $0.00139 |
Grade A, and why
changelog-release 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog & Release
Keep a Changelog for humans, SemVer for tooling, Conventional Commits as the source.
Release Flow
Collect commits since last tag → Derive bump → Move Unreleased → release →
Add date + version heading → Tag vX.Y.Z → Generate release notes → Push
Changelog Format (Keep a Changelog 1.1.0)
CHANGELOG.md lives at repo root, newest version on top, with a live
[Unreleased] section you append to as you merge.
# Changelog
All notable changes to this project are documented here.
Format: Keep a Changelog. Versioning: Semantic Versioning.
## [Unreleased]
## [1.4.0] - 2026-06-23
### Added
- OAuth login via GitHub (#231)
### Fixed
- Crash when config file is empty (#240)
## [1.3.1] - 2026-05-02
### Security
- Patch path-traversal in file upload (CVE-2026-1234)
[Unreleased]: https://example.com/repo/compare/v1.4.0...HEAD
[1.4.0]: https://example.com/repo/compare/v1.3.1...v1.4.0
[1.3.1]: https://example.com/repo/compare/v1.3.0...v1.3.1
The Six Categories
| Category | Use for |
|---|---|
| Added | New features |
| Changed | Changes to existing behavior |
| Deprecated | Soon-to-be-removed features (warn before Removed) |
| Removed | Features taken out this release |
| Fixed | Bug fixes |
| Security | Vulnerability fixes — always call out |
Write entries for humans: describe the user-visible effect, not the diff. Omit empty categories. Link issues/PRs.
Deriving the Version Bump
Read commit subjects since the last tag and map Conventional Commits → SemVer:
| Commit signal | Bump | Example |
|---|---|---|
BREAKING CHANGE: footer or feat!: / fix!: |
MAJOR X |
1.4.0 → 2.0.0 |
feat: |
MINOR Y |
1.4.0 → 1.5.0 |
fix: / perf: |
PATCH Z |
1.4.0 → 1.4.1 |
docs: chore: refactor: test: ci: style: |
none (unless paired with above) | — |
The highest signal wins: one feat! makes the whole release MAJOR.
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 · 163 lines · 84 tokens per session scan A d6a40b4217dc
changelog-release is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 84 tokens to every session and 1,393 once invoked, about $0.0003 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 skills, from other repositories
release-rollback
Plan and execute authorized release promotion or rollback with exact artifact and data compatibility. Use when deploying versions, changing traffic or recovering a bad release; do not equate reversing code with restoring data.
release-check
Use when cutting an Orchard release (tagging a new version of the FastAPI inventory service) — walks the pre-tag checklist so migrations, verify, changelog, and the tag stay in sync.
shared-tooling-changesets
Versioning and changelog management with @changesets/cli — adding changesets, version bumping, changelog generation, monorepo publishing, pre-release modes, and CI automation.
changelog-tracker
Monitors version changes with semantic versioning analysis and breaking change detection.
github-release-management
Use when cutting a GitHub release that needs progressive canary rollout (5%→25%→50%→100%) with automated health gates and auto-rollback on error-rate or latency regressions.
changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.