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/JordanGunn/nunchuckWrote 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/jordangunn/nunchuck/changelog-release)<a href="https://agentmods.dev/commands/jordangunn/nunchuck/changelog-release"><img src="https://agentmods.dev/badge/commands/jordangunn/nunchuck/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/commands/jordangunn/nunchuck/changelog-release"><img src="https://agentmods.dev/badge/commands/jordangunn/nunchuck/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.00000 | $0.00081 |
| Opus 5 | $0.00000 | $0.00041 |
| Sonnet 5 | $0.00000 | $0.00016 |
| Haiku 4.5 | $0.00000 | $0.00008 |
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 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.
What it actually says
changelog-release
Cut a release by transforming [Unreleased] into versioned section.
This command delegates to the agent skill at skills/changelog/changelog-release/.
Skill Root
- Path:
skills/
Skill Location
- Path:
skills/changelog/changelog-release/ - Manifest:
skills/changelog/changelog-release/SKILL.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.
- 11d ago First seen · 16 lines · 0 tokens per session scan A a3f08ba29af2
changelog-release is a command published in the GitHub repository JordanGunn/nunchuck (9 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 81 tokens. 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
ship
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision.
commit-push-pr
Commit, push, and open a PR.
generate-changelog
Generate a changelog from git history, grouping commits by type and version.
flow-release
Complete a feature/bugfix/hotfix flow by merging back to the target branch.
write-changelog
Generate a detailed changelog entry from git history and merged PRs.
release
Verify, sweep docs, cut a version — then hand the release sequence back.