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 Notysoty/openagentskills --skill changelog-curatorgit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/changelog-curator)<a href="https://agentmods.dev/skills/notysoty/openagentskills/changelog-curator"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/changelog-curator/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/notysoty/openagentskills/changelog-curator"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/changelog-curator.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.00026 | $0.01538 |
| Opus 5 | $0.00013 | $0.00769 |
| Sonnet 5 | $0.00005 | $0.00308 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
Changelog Curator 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Curator
What this skill does
This skill directs the agent to write or update a CHANGELOG.md that follows the Keep a Changelog format. It takes a list of commits, PR titles, or a git log dump, groups changes into the correct categories (Added, Changed, Fixed, Removed, Deprecated, Security), writes them in clear human-readable language, and formats the file correctly with semantic versioning and dates.
Use this before cutting a release, during sprint wrap-up, or when your changelog has fallen behind and you need to bring it up to date.
How to use
Claude Code / Cline
Copy this file to .agents/skills/changelog-curator/SKILL.md in your project root.
Then ask:
- "Use the Changelog Curator skill to update CHANGELOG.md for the v2.3.0 release. Here's the git log: [paste log]."
- "Use the Changelog Curator skill to create a CHANGELOG.md for these PRs: [list PRs]."
Provide:
- The git log (
git log --oneline vX.Y.Z..HEAD) or a list of PR titles/descriptions - The new version number and release date (or "Unreleased")
- The existing
CHANGELOG.mdif one exists (so the agent can append, not overwrite)
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane. Paste the git log or PR list along with the version number.
Codex
Paste the git log or PR list, the current CHANGELOG.md if it exists, and the version number. Ask Codex to follow the instructions below.
The Prompt / Instructions for the Agent
When asked to write or update a changelog, follow these steps:
Step 1 — Parse the input
The input may be:
- A raw
git log --onelinedump - A list of PR titles
- A mix of both
For each item, extract:
- The core change (ignore ticket numbers, PR numbers, merge commit boilerplate like "Merge branch X")
- The type of change (what category does it belong to?)
- The user-facing impact (what does a user or developer actually experience?)
Step 2 — Categorize each change
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 · 173 lines · 26 tokens per session scan A 9e385cf94b94
Changelog Curator is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 27d ago), licensed MIT. It adds 26 tokens to every session and 1,538 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-31.
Other skills, from other repositories
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.
semantic-release-automation
Automate versioning, changelog, tags, GitHub Releases, and npm publishing from Conventional Commits with semantic-release. Use when setting up or debugging automated releases, wiring a .releaserc / release config and the plugin pipeline (commit-analyzer, release-notes-generator, changelog, npm, git, github), making…