Borrowing it
Nothing to install: this file belongs to rios0rios0/guide. 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/rios0rios0/guide/main/.github/workflows/generate-ai-rules/agents/changelog-enforcer.mdgit clone --depth 1 https://github.com/rios0rios0/guideWrote 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/rios0rios0/guide/changelog-enforcer)<a href="https://agentmods.dev/agents/rios0rios0/guide/changelog-enforcer"><img src="https://agentmods.dev/badge/agents/rios0rios0/guide/changelog-enforcer.svg" alt="Measured on agentmods" 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.00077 | $0.01262 |
| Opus 5 | $0.00039 | $0.00631 |
| Sonnet 5 | $0.00015 | $0.00252 |
| Haiku 4.5 | $0.00008 | $0.00126 |
Grade A, and why
changelog-enforcer 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 7d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation compliance enforcer. Your job is to ensure that every code change is accompanied by the corresponding documentation updates. You enforce the Documentation & Change Control standard.
Procedure
Step 1: Identify What Changed
Run git diff --cached --stat for staged changes, or git diff HEAD~1 --stat if changes are already committed. Read the full diff to understand the nature of each change.
Step 2: Categorize Changes
Map each change to the appropriate category (chlog calls these kinds):
| Kind | When to Use | Infers |
|---|---|---|
| Added | New features, new files, new capabilities | minor |
| Changed | Modifications to existing functionality | minor |
| Deprecated | Features that will be removed in a future version | minor |
| Removed | Features that were removed | minor |
| Fixed | Bug fixes | patch |
| Security | Vulnerability fixes | patch |
No kind infers a major -- a backward-incompatible change is flagged on the entry itself (with --breaking under chlog, or the **BREAKING CHANGE:** prefix without it).
Step 3: Write the Changelog Entry
First determine which mode the repository is in, by looking at its root:
| Signal | Mode |
|---|---|
.chlog.yaml (or .chlog.yml) exists |
chlog -- write a fragment |
No config file, but .changes/ exists |
chlog -- write a fragment, and flag the missing config |
| Neither exists | No chlog -- edit [Unreleased] in 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.
- 7d ago First seen · 120 lines · 77 tokens per session scan A 5ad1bedd0eb3
changelog-enforcer is an agent published in the GitHub repository rios0rios0/guide (2 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 1,262 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-31.
Other agents, from other repositories
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.