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 basher83/lunar-claude --skill generate-changeloggit clone --depth 1 https://github.com/basher83/lunar-claudeWrote 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/basher83/lunar-claude/generate-changelog)<a href="https://agentmods.dev/skills/basher83/lunar-claude/generate-changelog"><img src="https://agentmods.dev/badge/skills/basher83/lunar-claude/generate-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/basher83/lunar-claude/generate-changelog"><img src="https://agentmods.dev/badge/skills/basher83/lunar-claude/generate-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.00504 |
| Opus 5 | $0.00008 | $0.00252 |
| Sonnet 5 | $0.00003 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
generate-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 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
Generate or update CHANGELOG.md using git-cliff based on conventional commits.
Action: $ARGUMENTS
If no action was specified, determine the workflow by asking the user.
Current State
Branch and status: !git status -sb
Recent commits: !git log --oneline -10
Latest tag: !git describe --tags --abbrev=0 2>/dev/null || echo "No tags yet"
Unpushed commits: !git log --oneline @{u}..HEAD 2>/dev/null || echo "No upstream or no unpushed commits"
Working directory: !git status --porcelain | head -5 || echo "Clean"
Unreleased changes preview: !git-cliff --unreleased 2>/dev/null | head -20 || echo "No unreleased changes or git-cliff not configured"
Pre-flight Check
If uncommitted changes exist (other than CHANGELOG.md), warn the user and ask whether to continue or abort.
If no conventional commits since last tag, inform user and stop.
Actions
preview: Show unreleased changes with git-cliff --unreleased. Report summary and stop.
generate: Run git-cliff -o CHANGELOG.md, show diff with git diff CHANGELOG.md, commit with message docs: update changelog.
release:
- Analyze unreleased commits to identify types of changes (breaking, features, fixes, docs, etc.)
- Check git-cliff recommendation:
git-cliff --bump --bumped-version - Recommend version bump level with reasoning (major/minor/patch) and show proposed version
- Ask user to confirm or override the bump level
- Generate changelog:
git-cliff --bump -o CHANGELOG.md - Show diff, commit:
docs: update changelog for v<VERSION> - Create annotated tag:
git tag -a v<VERSION> -m "Release v<VERSION>"
Summary
Report changelog diff summary, version change (if releasing), and next step:
- If committed: "Ready to push with
git push" - If released: "Ready to push with
git push && git push --tags"
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 · 56 lines · 16 tokens per session scan A 7d9f558b084f
generate-changelog is a skill published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 504 once invoked, about $0.0001 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 skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.