Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tmj-90/gaffernpx agentmods add skills/tmj-90/gaffer/changelog-generatorWrote 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/tmj-90/gaffer/changelog-generator)<a href="https://agentmods.dev/skills/tmj-90/gaffer/changelog-generator"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/changelog-generator/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/tmj-90/gaffer/changelog-generator"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/changelog-generator.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.00068 | $0.00956 |
| Opus 5 | $0.00034 | $0.00478 |
| Sonnet 5 | $0.00014 | $0.00191 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
changelog-generator 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 9d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate consistent, auditable release notes
Conventional Commits → semantic bump → Keep a Changelog. Three steps, always in order.
Conventional Commit → Semantic Bump
| Commit type | Bump |
|---|---|
feat: |
MINOR |
fix:, perf: |
PATCH |
BREAKING CHANGE: footer or ! suffix |
MAJOR |
refactor:, docs:, chore:, ci:, test: |
No version bump |
Multiple commits in a release: take the highest-ranking bump. One feat: in a release of ten fix: commits → MINOR bump.
Keep a Changelog sections
## [1.4.0] — 2026-06-28
### Added
- feat commits
### Changed
- refactor commits; BREAKING CHANGE goes here with migration note
### Deprecated
### Removed
### Fixed
- fix commits
### Security
- security commits
Use ISO 8601 dates (YYYY-MM-DD). Link version headers to the git tag diff URL.
Git range commands
# Commits between two tags
git log v1.3.0..v1.4.0 --pretty=format:'%s'
# Commits since last tag to HEAD
git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:'%s'
# With author and hash (for detailed notes)
git log v1.3.0..v1.4.0 --pretty=format:'%h %an %s'
CI integration pattern
# .github/workflows/release.yml (excerpt)
- name: Generate changelog
run: |
git log ${{ env.PREV_TAG }}..HEAD --pretty=format:'%s' \
| python scripts/generate_changelog.py \
--next-version ${{ env.NEXT_VERSION }} \
--format markdown >> CHANGELOG.md
Block the pipeline if commit messages don't follow Conventional Commits format — a linting step before changelog generation prevents garbage output.
Commit message linting rules
A valid Conventional Commit: <type>(<optional scope>): <description>
Valid types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.
Reject: commits with no type prefix; commits with WIP: prefix; commits longer than 72 characters in the subject line.
Steps
- Get the commit range. Tag-to-tag or last-tag-to-HEAD.
- Parse commit messages. Classify each as feat / fix / breaking / no-bump.
- Compute semantic bump. Take the maximum across all commits in the range.
- Group into Keep a Changelog sections. Added / Changed / Fixed / Security.
- Write the changelog entry. Date, version, sections. Link version to git tag diff.
- Lint commit messages before finalising — reject any that don't conform.
- Verify. Check that the computed version matches the expected bump; confirm the changelog entry renders correctly in Markdown preview.
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.
- 9d ago First seen · 103 lines · 68 tokens per session scan A e8fb1dd812d8
changelog-generator is a skill published in the GitHub repository tmj-90/gaffer (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 956 once invoked, about $0.0003 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
aiwg-pr
AIWG-specific pull request delivery workflow for AIWG product/workspace changes; not the generic repository PR process.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
git-mirror-audit
Verify configured secondary git mirrors are present and not drifting from the primary remote/default branch.
aiwg-delivery-pr
AIWG-specific delivery pull request workflow; explicit alias for aiwg-pr, not a generic repository PR guide.
writing-changelogs
Writes human-friendly changelog entries and release notes. Use when populating changelog, preparing releases, or reviewing release notes quality.
code-review-loop
Iterative review+fix loop for BASESHA..HEAD: generate findings, apply accepted fixes, run checks, commit, and re-review up to 3 iterations or until clean.