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.
npx agentmods add skills/soulcodex/agentic/write-changelognpx skills add soulcodex/agentic --skill write-changeloggit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/write-changelog)<a href="https://agentmods.dev/skills/soulcodex/agentic/write-changelog"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/write-changelog.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 | $0.00073 | $0.00498 |
| Opus 5 | $0.00036 | $0.00249 |
| Sonnet 5 | $0.00015 | $0.00100 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
write-changelog 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 3d 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
Write Changelog Skill
Generate a CHANGELOG.md entry for the next release.
Step 1 — Determine the Version
Ask the user for the new version number (SemVer) if not provided.
Step 2 — Gather Commits
Run: git log {last-tag}..HEAD --oneline --no-merges
If no previous tag exists: git log --oneline --no-merges
Step 3 — Categorize Changes
Group commits by their Conventional Commit type:
| Commit type | Changelog section |
|---|---|
feat |
Added |
fix |
Fixed |
refactor, perf |
Changed |
docs |
Changed |
BREAKING CHANGE footer |
(prefix with **BREAKING**) |
chore, ci, build |
(omit from changelog) |
Step 4 — Write the Entry
Format:
## [{{VERSION}}] - {{DATE}}
### Added
- Description of new feature (refs #issue)
### Changed
- Description of change (refs #issue)
### Fixed
- Description of bug fix (refs #issue)
### Removed
- Description of removed feature (refs #issue)
- Each item starts with a capital letter, no period at the end.
- Include issue/PR references where available.
- Write from the user's perspective — what changed for them, not what code changed.
Step 5 — Insert into CHANGELOG.md
Prepend the new entry below the # Changelog header and above previous entries.
If no CHANGELOG.md exists, create it with the standard header first.
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.
- 3d ago First seen · 77 lines · 73 tokens per session scan A bf66b01645a5
write-changelog is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 3d ago), licensed MIT. It adds 73 tokens to every session and 498 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 skills, from other repositories
release
Guide the Backend.AI release process - run release.sh, generate changelog via towncrier, consolidate RC entries for final releases with subsection grouping.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
Release Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
submit
Complete submission workflow - quality checks, commit, PR creation, changelog generation, and final push. Use after finishing implementation work.
Changelog Curator
Maintains and formats a CHANGELOG.md following Keep a Changelog conventions from git history or PR list.