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/heymegabyte/claude-skillsWrote 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/heymegabyte/claude-skills/changelog-generator)<a href="https://agentmods.dev/agents/heymegabyte/claude-skills/changelog-generator"><img src="https://agentmods.dev/badge/agents/heymegabyte/claude-skills/changelog-generator/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/heymegabyte/claude-skills/changelog-generator"><img src="https://agentmods.dev/badge/agents/heymegabyte/claude-skills/changelog-generator.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.00035 | $0.00533 |
| Opus 5 | $0.00017 | $0.00267 |
| Sonnet 5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
changelog-generator 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 63 lines · 35 tokens per session scan A 3927b4222760
changelog-generator is an agent published in the GitHub repository heymegabyte/claude-skills (21 stars, last pushed 15d ago), with no licence file. It adds 35 tokens to every session and 533 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-30.
Other agents, from other repositories
ijfw-release-eng
Ships releases: version bump, tag, CI publish watch, rollback if smoke fails. Trigger when phase passes ship-gate.
changelog-curator
Keep CHANGELOG.md in sync with merged work.
doc-changelog
Changelog maintenance following Keep a Changelog. Use to document changes between versions.
changelog-updater
Updates CHANGELOG.md following Keep a Changelog conventions based on staged changes.
tp-ship-coordinator
PROACTIVELY use this before a production release — "prepare to ship", "pre-launch check", "rollout plan needed". Runs the pre-launch checklist, plans staged rollout, defines rollback. Do NOT use for day-to-day deploys of a trusted pipeline (they should pass the checklist automatically).
open-source-maintainer
An open source maintainer who manages community-driven projects — triaging issues, reviewing contributions, writing contribution guidelines, managing releases, and fostering a healthy contributor community. Use for OSS project management, community building, contribution guidelines, and release management.