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.
git clone --depth 1 https://github.com/Chemaclass/agnostic-aiWrote 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/agents/chemaclass/agnostic-ai/changelog-curator)<a href="https://agentmods.dev/agents/chemaclass/agnostic-ai/changelog-curator"><img src="https://agentmods.dev/badge/agents/chemaclass/agnostic-ai/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/agents/chemaclass/agnostic-ai/changelog-curator"><img src="https://agentmods.dev/badge/agents/chemaclass/agnostic-ai/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.00015 | $0.00257 |
| Opus 5 | $0.00008 | $0.00129 |
| Sonnet 5 | $0.00003 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
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.
What it actually says
You keep CHANGELOG.md accurate for the next release.
When invoked:
- Read
CHANGELOG.mdto learn the current## [Unreleased]state. - Run
git log --oneline <last-tag>..HEADto list commits since the last release. - For every user-visible commit (
feat:,fix:,docs:that change behavior), add a single-line bullet under the correct subsection of## [Unreleased]:### Addedfor new features, new adapters, new flags.### Changedfor behavior changes that are not bugs.### Fixedfor bug fixes.### Removedfor deletions.
- Skip pure refactors, internal tests, CI noise, and dependency bumps unless they affect users.
- Reference the PR with
(#N)when known. - Keep entries one short sentence each. Lead with the action.
Do not invent entries. If a commit message is ambiguous, read the diff.
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 · 25 lines · 15 tokens per session scan A 65dd29824dd2
changelog-curator is an agent published in the GitHub repository Chemaclass/agnostic-ai (12 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 257 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 agents, from other repositories
release_manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
devops-engineer
Designs CI/CD pipelines, provisions cloud infrastructure, and manages releases. Absorbed cloud-engineer and release-manager responsibilities. Runs as the sole Ship phase agent. Use when building CI pipelines, deploying to cloud, or managing releases.
doc-changelog
Changelog maintenance following Keep a Changelog. Use to document changes between versions.
godmode-shipping
Release Gatekeeper, QA & Verification Auditor. Runs the automated quality gate (lint, typecheck, tests, a11y, seo) after Reviewer's findings are all fixed/wontfix — Reviewer and Shipping are deliberately two different checks (adversarial correctness review vs. mechanical gate execution), not one merged step. Ensures…
release-changelog-composer
Compose the prose of one release cut from the records that shipped in it — every line citing the record id it reports, so the binary can prove the release record describes exactly the cut. Host-delegated; feeds abcd launch ship --changelog-json.
changelog-updater
Updates CHANGELOG.md following Keep a Changelog conventions based on staged changes.