Borrowing it
Nothing to install: this file belongs to umbraco/Umbraco.Automate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/umbraco/Umbraco.Automate/v18/dev/.claude/skills/changelog-management/SKILL.mdgit clone --depth 1 https://github.com/umbraco/Umbraco.AutomateWrote 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/umbraco/umbraco.automate/changelog-management)<a href="https://agentmods.dev/skills/umbraco/umbraco.automate/changelog-management"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco.automate/changelog-management/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/umbraco/umbraco.automate/changelog-management"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco.automate/changelog-management.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.00038 | $0.00715 |
| Opus 5 | $0.00019 | $0.00358 |
| Sonnet 5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
changelog-management 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Manager
You are helping generate changelogs for Umbraco.Automate products from conventional commit history.
Task
Generate or update CHANGELOG.md files for products using the changelog generation scripts.
How Changelogs Work
- Each product has a
CHANGELOG.mdat its root - Auto-generated from git history using Conventional Commits
- Each product has a
changelog.config.jsondefining its commit scopes - CI validates changelogs on
vN/release/*andvN/hotfix/*branches
Available Commands
List Products
npm run changelog:list
Generate Changelog
# For a specific version
npm run changelog -- --product=Umbraco.Automate --version=1.1.0
# For unreleased changes
npm run changelog -- --product=Umbraco.Automate --unreleased
PowerShell Wrapper
.\scripts\generate-changelog.ps1 -Product Umbraco.Automate -Version 1.1.0
Bash Wrapper
./scripts/generate-changelog.sh --product=Umbraco.Automate --version=1.1.0
Workflow
-
Ask user for input:
- List available products or let user specify
- Ask for version number (or use --unreleased flag)
- Platform preference (npm, PowerShell, or Bash)
-
Run the appropriate command
-
Verify the changelog was updated:
- Read the generated CHANGELOG.md
- Show the new entry to the user
-
Remind about next steps:
- Review the generated changelog
- Edit if needed (add breaking changes details, etc.)
- Commit the changes
Available Products
Products are auto-discovered by scanning for changelog.config.json files:
- Umbraco.Automate (core)
Important Notes
- Always run from repository root
- Use
--unreleasedfor preview before creating release branch - Version must match the version in
version.json - CI will fail if changelog is missing or outdated on release branches
Example Flow
User invokes: /changelog-management
You ask: "Which product?" (list available)
User selects: Umbraco.Automate
You ask: "What version?" (or suggest --unreleased)
User provides: 1.1.0
You detect: Windows platform
You run: .\scripts\generate-changelog.ps1 -Product Umbraco.Automate -Version 1.1.0
You verify: Read Umbraco.Automate/CHANGELOG.md and show the new entry
You remind:
- Review the generated content
- Edit if needed
- Commit the updated CHANGELOG.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 · 109 lines · 38 tokens per session scan A f27519f00c50
changelog-management is a skill published in the GitHub repository umbraco/Umbraco.Automate (5 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 715 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-31.
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.