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 skills add manu14357/zskills --skill changelog-generatorgit clone --depth 1 https://github.com/manu14357/zskillsWrote 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/manu14357/zskills/changelog-generator)<a href="https://agentmods.dev/skills/manu14357/zskills/changelog-generator"><img src="https://agentmods.dev/badge/skills/manu14357/zskills/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/manu14357/zskills/changelog-generator"><img src="https://agentmods.dev/badge/skills/manu14357/zskills/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.00040 | $0.01339 |
| Opus 5 | $0.00020 | $0.00669 |
| Sonnet 5 | $0.00008 | $0.00268 |
| Haiku 4.5 | $0.00004 | $0.00134 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generator
Use This Skill When
- Preparing release notes for a new product version
- Creating weekly or monthly product update summaries
- Documenting changes for customers or stakeholders
- Writing app store changelog submissions
- Generating update notifications for users
- Maintaining public changelog or product update pages
- Creating internal release documentation
- Need to transform commits into customer-facing language
When NOT to Use
- Internal developer documentation (keep technical commit language)
- When commits already have clear user-facing descriptions
- For non-git version control systems
- When detailed technical accuracy is required for developers
- For automated CI/CD commit logs (use raw commits instead)
Context: Changelog Maturity
Undeveloped: Raw git commits listed, technical jargon, unclear for customers.
Target: Commits categorized by type, translated to user language, grouped logically, professional formatting.
Optimized: Polished changelog with strategic storytelling, emphasis on customer impact, brand voice, multimedia integration.
Core Principle
Users deserve clear, accessible changelogs that celebrate product improvements. Transform technical commits into customer language that highlights impact, not implementation.
Instructions
Step 1: Gather Commit History
Identify the scope:
| Scope Type | Example | Use Case |
|---|---|---|
| Date Range | "March 1–15" | Weekly/monthly updates |
| Version Range | "v2.4.0 to v2.5.0" | Release-specific |
| Time Period | "Last 7 days" | Recent changes |
| Branch | "main since last release" | Staged features |
Command pattern (provide to user):
Get all commits from [DATE] to [DATE]
or
Get all commits between version [V1] and [V2]
or
Get all commits from the past [N] days
Step 2: Categorize Changes
Standard Categories:
| Category | Indicators | Icon |
|---|---|---|
| Features | "feat:", new functionality, user-facing | ✨ |
| Improvements | "perf:", "improve", speed, UX enhancements | 🔧 |
| Bug Fixes | "fix:", "resolved", issues, errors | 🐛 |
| Breaking Changes | "BREAKING", incompatible changes | ⚠️ |
| Security | "security", "CVE", vulnerability fixes | 🔒 |
| Documentation | "docs:", guides, README, help | 📖 |
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.
- 12d ago First seen · 186 lines · 40 tokens per session scan A f8dc29d19bec
changelog-generator is a skill published in the GitHub repository manu14357/zskills (16 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,339 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…