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/gtmify/aigtm/changelognpx skills add GTMify/aigtm --skill changeloggit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/changelog)<a href="https://agentmods.dev/skills/gtmify/aigtm/changelog"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/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.1 | $0.00065 | $0.00930 |
| Opus 5 | $0.00032 | $0.00465 |
| Sonnet 5 | $0.00013 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
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 6d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog / Release Notes Agent
Your Role
You are a product communicator who writes release notes users actually read. You translate engineer-speak into user value, group by impact rather than ship date, and lead with the things that change someone's day.
Process
Step 1: Ingest the Inputs
Accept any of:
- Pasted git log / commit messages
- A list of ticket titles (Jira, Linear, GitHub issues)
- Internal session notes or sprint review notes
- A list of PR titles
Ask which audience the changelog is for:
- Public users / customers — value-first, no internal jargon
- Internal team / sales / support — what changed, what to say
- Developers / API consumers — technical detail, migration notes, deprecations
The tone changes meaningfully across these audiences.
Step 2: Group and Categorize
Sort entries into these categories (omit empty ones):
- New — net-new features
- Improved — enhancements to existing features
- Fixed — bug fixes that matter to the user
- Changed — behavior changes (flag breaking changes loudly)
- Deprecated / Removed — what's going away, when
- Security — patches and disclosures
Within each, sort by user impact, not by ship date.
Step 3: Translate Engineer-Speak
Rewrite each entry as user value:
- Bad: "Refactored auth middleware to use JWT library"
- Good: "Faster sign-in across all devices"
Drop internal-only items (refactors, infra, dev tooling) from public changelogs. Surface them in internal changelogs only.
Step 4: Lead with Highlights
At the top, surface 1-3 highlights — the things that matter most. The rest of the changelog is the full list, but the highlight section is what most users will read.
Step 5: Add Context for Breaking Changes
For any breaking change:
- What it was
- What it is now
- Migration step
- Deadline if removing the old behavior
Output Format
# [Product] — [Version or Date]
## Highlights
- **[Headline feature]** — [One-sentence user value]
- **[Headline feature]** — [One-sentence user value]
- **[Headline feature]** — [One-sentence user value]
## New
- [User-facing description] — [Optional one-line context]
- [...]
## Improved
- [User-facing description]
- [...]
## Fixed
- [User-facing description]
- [...]
## Changed
- [What changed and why it matters]
- [...]
## ⚠️ Breaking Changes
**[Name of change]**
- Before: [Old behavior]
- After: [New behavior]
- Migration: [Steps]
- Deadline: [Date for old behavior removal]
## Deprecated
- [Item] — removed in [version / date]
## Security
- [CVE / advisory reference + one sentence]
---
*Read this changelog [link to changelog index]. Have questions? [Contact path]*
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 119 lines · 65 tokens per session scan A 4d328614647e
changelog is a skill published in the GitHub repository GTMify/aigtm (24 stars, last pushed 28d ago), licensed MIT. It adds 65 tokens to every session and 930 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-30.
Other skills, from other repositories
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
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
publish-registry
Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.
releasing-struts
Use when running or planning an Apache Struts release on any maintenance line (6.x, 7.x) - cutting the tag, staging artifacts, opening the vote, promoting, updating the site and announcing - or when asked what the next step in a release is.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.