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 RockaRhymeLLC/claude-code-skills --skill smart-changeloggit clone --depth 1 https://github.com/RockaRhymeLLC/claude-code-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/skills/rockarhymellc/claude-code-skills/smart-changelog)<a href="https://agentmods.dev/skills/rockarhymellc/claude-code-skills/smart-changelog"><img src="https://agentmods.dev/badge/skills/rockarhymellc/claude-code-skills/smart-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/rockarhymellc/claude-code-skills/smart-changelog"><img src="https://agentmods.dev/badge/skills/rockarhymellc/claude-code-skills/smart-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.00060 | $0.01924 |
| Opus 5 | $0.00030 | $0.00962 |
| Sonnet 5 | $0.00012 | $0.00385 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
smart-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.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Changelog Generator
Generate professional changelogs and release notes from your git history.
When to Activate
- User says
/smart-changelog, "generate changelog", "release notes", or "what changed" - User wants to prepare a release
- User asks about version bumping or semantic versioning
Instructions
Step 1: Determine the Range
Figure out what commits to include:
# List recent tags
git tag --sort=-version:refname | head -10
# Find the latest tag
git describe --tags --abbrev=0 2>/dev/null || echo "no tags"
# If no tags, use the first commit
git rev-list --max-parents=0 HEAD
Range logic:
- If user specifies a range (e.g., "since v1.2.0"): use that
- If tags exist: use
<latest-tag>..HEAD - If no tags: use all commits (first release)
Ask the user if unclear:
- "I see the latest tag is
v1.3.0. Should I generate changes since then?" - "No tags found — should I include all commits, or specify a starting point?"
Step 2: Gather Commits
# Full commit log with hash, subject, body, and author
git log <range> --format='%H|%s|%b|%an' --no-merges
# Or with merge commits if the project uses merge-based workflow
git log <range> --format='%H|%s|%b|%an' --first-parent
Also check for:
# Any breaking changes?
git log <range> --grep='BREAKING' --format='%H %s'
# Linked issues/PRs?
git log <range> --grep='#[0-9]' --format='%H %s'
Step 3: Categorize Commits
If the project uses Conventional Commits:
Parse the type prefix to categorize:
| Type | Category | Emoji |
|---|---|---|
feat |
Added | ✨ |
fix |
Fixed | 🐛 |
perf |
Performance | ⚡ |
refactor |
Changed | ♻️ |
docs |
Documentation | 📚 |
test |
Tests | 🧪 |
chore |
Maintenance | 🔧 |
ci |
CI/CD | 🏗️ |
style |
Style | 🎨 |
revert |
Reverted | ⏪ |
BREAKING CHANGE |
Breaking | 💥 |
If NOT using Conventional Commits:
Analyze each commit's diff and message to categorize:
# Get the diff stat for context
git show --stat <hash>
What ships with it
1 file 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.
- 11d ago First seen · 243 lines · 60 tokens per session scan A 0825e4af39e4
smart-changelog is a skill published in the GitHub repository RockaRhymeLLC/claude-code-skills (1 stars, last pushed 6mo ago), licensed MIT. It adds 60 tokens to every session and 1,924 once invoked, about $0.0003 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
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
update-changelog
Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
git
Granular git operations with conventional commits - stage, commit, push, PR, merge. Auto-splits commits by type/scope, blocks on secrets, delegates verbose work to git-manager subagent. GitHub CLI conventions: --body-file for PR bodies, treat gh pr checks exit 8 (pending) as retry not failure, guard run-id assignment…
skill-management
Manage the lifecycle of agent skills in this repo - create new skills via skill-creator, pull/sync upstream skills with the vd CLI, validate frontmatter, bump versions, and ship releases through conventional commits. Use when the user says 'create a skill', 'add a skill', 'sync skills', 'release vd', 'bump version'…