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 yu-iskw/coding-agent-fabric --skill manage-changeloggit clone --depth 1 https://github.com/yu-iskw/coding-agent-fabricWrote 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/yu-iskw/coding-agent-fabric/manage-changelog)<a href="https://agentmods.dev/skills/yu-iskw/coding-agent-fabric/manage-changelog"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/manage-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/skills/yu-iskw/coding-agent-fabric/manage-changelog"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/manage-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.00038 | $0.00394 |
| Opus 5 | $0.00019 | $0.00197 |
| Sonnet 5 | $0.00008 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
manage-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 10d 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.
What it actually says
Manage Changelog Skill
This skill enables the agent to manage project changelogs efficiently using Changie. It supports the full lifecycle from initialization to release.
When to Use
- When you need to initialize a changelog for a new project.
- When you want to record a change (feature, bug fix, etc.) after completing a task.
- When preparing for a new release and batching unreleased changes.
Instructions
1. Initialization
If the project doesn't have changie set up, run the initialization script:
.claude/skills/manage-changelog/scripts/init-changie.sh
This will create .changie.yaml with standard workspace settings.
2. Adding Changes
To add a new change fragment:
changie new --kind <kind> --body "<description>"
- Kinds: Typically
feat,fix,docs,refactor,test,chore. - Helper Script: Alternatively, use
.claude/skills/manage-changelog/scripts/add-from-last-commit.shto create a fragment from the last commit message.
3. Batching a Release
When you are ready to create a new version:
# Preview next version
changie next auto
# Batch unreleased changes into a version
changie batch auto
4. Merging into CHANGELOG.md
To update the main CHANGELOG.md file:
changie merge
References
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 62 lines · 38 tokens per session scan A 7bc142e78dbf
manage-changelog is a skill published in the GitHub repository yu-iskw/coding-agent-fabric (1 stars, last pushed 9d ago), licensed Apache-2.0. It adds 38 tokens to every session and 394 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
deploy-npm
Release an npm package: version, CHANGELOG, publish, verify. Use when "publish this package", "release to npm", or "ship a new npm version". Running-app production deploy → workflow-ship-and-observe.
deployment-checklist-generator
Creates comprehensive deployment checklists with pre-deployment checks, smoke tests, verification steps, and sign-off workflows. Use for "deployment checklist", "release verification", "deployment runbook", or "production readiness".
changelog-writer
Generates changelogs and release notes from git commits, PR titles, and issue references. Organizes changes by impact type (breaking, features, fixes, improvements), formats according to Keep a Changelog standard, and provides version tagging and semantic versioning suggestions. Use when users request "create…
release-automation-builder
Automates releases and package publishing with changesets or semantic-release. Handles versioning, changelog generation, git tags, and release notes. Use for "release automation", "semantic versioning", "package publishing", or "changelog generation".
changelog
Changelog Generation Command 📝.
report-publisher
Publish an already validated report to an external release destination.