changelog-enforcer

changelog-enforcer is a skill for Claude Code, Codex from strikersam/autonomous-ai-agency. It costs 33 tokens per session (747 once invoked), scanned A, original, MIT.

A rule for recording meaningful code changes in a changelog, a document that lists what changed between releases.

In plain words
What is it for?
Use it before committing changes to update docs/changelog.md under the appropriate Unreleased category.
Why use it?
It keeps feature, behavior, bug-fix, and security changes visible to the team and users before a commit is made.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

Good fit Use it before committing changes to update docs/changelog.md under the appropriate Unreleased category.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/strikersam/autonomous-ai-agency/changelog-enforcer
Install

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.

Any agent
npx skills add strikersam/autonomous-ai-agency --skill changelog-enforcer
Clone the repo
git clone --depth 1 https://github.com/strikersam/autonomous-ai-agency

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for changelog-enforcer

README.md
[![agentmods](https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/changelog-enforcer/github.svg)](https://agentmods.dev/skills/strikersam/autonomous-ai-agency/changelog-enforcer)
Your own site
<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/changelog-enforcer"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/changelog-enforcer/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.

agentmods 80×15 button for changelog-enforcer

Your own site · 80×15
<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/changelog-enforcer"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/changelog-enforcer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 747 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00747
Opus 5 $0.00016 $0.00374
Sonnet 5 $0.00007 $0.00149
Haiku 4.5 $0.00003 $0.00075

Measured 12d ago against content hash 96a924167c12, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 12d 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.

.agents/skills/changelog-enforcer/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: changelog-enforcer

When to Use

Before EVERY commit that is not purely:

  • chore: — dependency bumps, tooling config
  • docs: — doc-only changes (unless the doc IS the changelog)
  • style: — formatting only
  • ci: — CI/workflow-only changes
  • test: — test-only additions with no behaviour change

If in doubt, add a changelog entry. Entries are cheap; missing them causes release confusion.

Changelog Location

docs/changelog.md — follows Keep a Changelog format.

Entry Format

Add under ## [Unreleased] at the top of the file:

## [Unreleased]

### Added
- Brief description of new feature or capability. (#PR or commit reference if known)

### Changed
- What existing behaviour changed and how.

### Fixed
- What bug was fixed and what the symptom was.

### Security
- Any change touching auth, API keys, secrets, or access control.

### Removed
- Features, endpoints, or options that were removed.

Only include subsections that are relevant to the commit.

Instructions

  1. Read docs/changelog.md to find the [Unreleased] block.
  2. Add a new entry under the appropriate subsection.
  3. Be specific: mention the module, the route, or the behaviour that changed.
  4. Include the reason if non-obvious.
  5. Stage docs/changelog.md alongside the code change.

Examples

Good entries:

### Added
- `router/registry.py` — `fast_response` category routes short streaming requests to `qwen3-coder:7b` (lightest model) to reduce latency.

### Fixed
- `agent/loop.py` — `_parse_execution_response` now handles Windows-style CRLF line endings without corrupting file content.

### Security
- `key_store.py` — API keys are now hashed with SHA-256 before storage; plain-text keys are no longer written to `keys.json`.

Bad entries (too vague):

### Changed
- Updated some stuff.
- Fixed bug.

Acceptance Checks

  • docs/changelog.md has at least one new entry under [Unreleased]
  • Entry uses correct subsection (Added / Changed / Fixed / Security / Removed)
  • Entry names the specific file or feature that changed
  • git diff --cached -- docs/changelog.md shows staged changes
  • CI changelog-check job will pass (see .github/workflows/changelog-check.yml)

Read the full file on GitHub · 100 lines

Changes

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.

  1. 12d ago First seen · 100 lines · 33 tokens per session scan A 96a924167c12

Subscribe to this mod's changes

changelog-enforcer is a skill published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 747 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.

Related

Other skills, from other repositories