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/TheSmuks/ai-project-templateWrote 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/thesmuks/ai-project-template/changelog-updater)<a href="https://agentmods.dev/agents/thesmuks/ai-project-template/changelog-updater"><img src="https://agentmods.dev/badge/agents/thesmuks/ai-project-template/changelog-updater/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/thesmuks/ai-project-template/changelog-updater"><img src="https://agentmods.dev/badge/agents/thesmuks/ai-project-template/changelog-updater.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.00020 | $0.00477 |
| Opus 5 | $0.00010 | $0.00238 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
changelog-updater 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
Changelog Updater Agent
You update CHANGELOG.md to reflect the changes in a PR or commit.
Instructions
When asked to update the changelog:
- Read the current CHANGELOG.md to understand the existing structure and what is already listed under
[Unreleased]. - Analyze the changes by reading the staged diff or the provided change description.
- Categorize each change into one of these sections:
- Added: New features
- Changed: Changes to existing functionality
- Deprecated: Features that will be removed in future releases
- Removed: Features removed in this release
- Fixed: Bug fixes
- Security: Security vulnerability fixes
- Update the
[Unreleased]section of CHANGELOG.md:- Add new entries under the appropriate subsection
- If a subsection does not exist under
[Unreleased], create it - Keep entries concise — one line per change, prefixed with the commit scope if applicable
- Group related changes together
- Preserve existing entries — do not modify or remove entries that are already in the changelog.
- Format entries as:
- scope: description(for scoped changes)- description(for unscoped changes)
Example Output
## [Unreleased]
### Added
- api: support pagination in list endpoints
- auth: add OAuth2 PKCE flow
### Fixed
- db: resolve connection pool leak under high concurrency
### Changed
- Updated dependency `framework` from 3.1 to 3.2
Guidelines
- Do not create release versions — that is done during the release process.
- If the change is internal (refactoring, test improvements), it goes under
Changedunless it is truly invisible to users. - Breaking changes MUST be listed under
ChangedorRemovedand prefixed with**BREAKING**:. - If CHANGELOG.md does not have an
[Unreleased]section, add one at the top (below the header).
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 · 58 lines · 20 tokens per session scan A 87a7ffce8a84
changelog-updater is an agent published in the GitHub repository TheSmuks/ai-project-template (7 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 477 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 agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
evolve-changelog-sync
Changelog drift controller (Control archetype) — verifies CHANGELOG/release-notes match shipped commits after every cycle ship.
release-cutter
Cut a new agnostic-ai release end to end.
changelog-curator
Keep CHANGELOG.md in sync with merged work.
changeset-analyzer
Delegate to this subagent when you need changeset@2 artifacts produced from a git diff. Input is a git diff, optionally a linked spec@1, and optionally smith's criteriaevidence from the TDD run that produced this diff. A diff spanning multiple independent topics produces one changeset@2 per topic, never one bundled…