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 kajitiluna/erd-designer --skill update-changeloggit clone --depth 1 https://github.com/kajitiluna/erd-designerWrote 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/kajitiluna/erd-designer/update-changelog)<a href="https://agentmods.dev/skills/kajitiluna/erd-designer/update-changelog"><img src="https://agentmods.dev/badge/skills/kajitiluna/erd-designer/update-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/kajitiluna/erd-designer/update-changelog"><img src="https://agentmods.dev/badge/skills/kajitiluna/erd-designer/update-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.00075 | $0.00622 |
| Opus 5 | $0.00037 | $0.00311 |
| Sonnet 5 | $0.00015 | $0.00124 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
update-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 12d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update CHANGELOG
Generate a user-facing CHANGELOG.md entry from the git changes between main and the current branch.
Step 1: Gather information
date +%Y%m%d # today's date → version number
git log main..HEAD --oneline # commits on this branch
git diff main..HEAD # full diff for analysis
Step 2: Identify user-facing changes
Analyze the diff from the user's perspective — what they can do differently, not how the code changed.
Include:
- New features, UI options, menu items, commands, or keyboard shortcuts
- Behavior changes visible to the user (defaults, layout, export output, etc.)
- Bug fixes that affected users (what broke, in what scenario)
- New file format support or protocol options
Exclude:
- Internal refactoring, code cleanup, or abstraction changes
- Test additions or fixes
- Dependency version bumps (unless they fix a user-visible bug)
- Build/CI configuration changes
- Developer tooling (guidelines, linter config, etc.)
If there are no user-facing changes, state that clearly instead of inventing entries.
Step 3: Generate the entry
Version format: 0.{yyyyMMdd} using today's date from Step 1.
Follow the existing CHANGELOG.md format exactly:
## [0.yyyyMMdd] - yyyy-MM-dd
### Added
- **Feature Title**:
One to three sentences describing what was added, from the user's perspective.
What can users do now that they couldn't before?
### Changed
- **Change Title**:
What changed and how it affects users.
### Fixed
- **Fix Title**:
What was broken, in what scenario, and what is now correct.
Formatting rules:
- Only include sections (
### Added,### Changed,### Fixed) that have content - Bold title on the bullet line, followed by a colon
- Body indented with two spaces, separated from the title line by a blank line
- English only, concise, present tense ("Users can now...", "The dialog now shows...")
- Group multiple related sub-points under one bullet using indented sub-bullets if needed
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.
- 12d ago First seen · 85 lines · 75 tokens per session scan A 196a8158784b
update-changelog is a skill published in the GitHub repository kajitiluna/erd-designer (21 stars, last pushed today), licensed Apache-2.0. It adds 75 tokens to every session and 622 once invoked, about $0.0004 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.