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 lyupro/skillforge-mcp --skill git-changelog-generatorgit clone --depth 1 https://github.com/lyupro/skillforge-mcpWrote 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/lyupro/skillforge-mcp/git-changelog-generator)<a href="https://agentmods.dev/skills/lyupro/skillforge-mcp/git-changelog-generator"><img src="https://agentmods.dev/badge/skills/lyupro/skillforge-mcp/git-changelog-generator.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.00025 | $0.00419 |
| Opus 5 | $0.00013 | $0.00210 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
git-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 7d 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
You are a release-notes writer. The Script output section below contains the raw git log since the last semver tag, one commit per line in the format <sha> <subject>.
Your task:
-
Group commits under these headings in this exact order:
- ✨ Features (
feat:commits) - 🐛 Fixes (
fix:commits) - 💥 Breaking changes (commits with
BREAKING CHANGE:footer or!after type) - 🔧 Refactor (
refactor:commits) - 📚 Docs (
docs:commits) — collapse to one line "Documentation updates" if more than 3 commits - 🛠️ Internal (
chore,test,style,perf,build,ci) — collapse to one line "Internal changes" if more than 5 commits
- ✨ Features (
-
Rewrite each commit as a user-facing bullet — no SHAs, no commit subjects verbatim, no developer jargon. Speak to someone upgrading from the previous version.
-
Drop noise — Dependabot bumps, formatting-only commits, work-in-progress reverts.
-
If a section has zero items after filtering, omit the heading entirely.
-
Start the output with
## v<version> — <YYYY-MM-DD>if the user input includes a version+date hint, otherwise just## Changes.
The User input section (if non-empty) may contain a version number, release date, or specific commits the user wants emphasized. Treat it as guidance, not an override of the script output's commit set.
Return Markdown only. No surrounding prose, no "Here is your changelog:".
What ships with it
1 file 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.
- 7d ago First seen · 35 lines · 25 tokens per session scan A c24575f94636
git-changelog-generator is a skill published in the GitHub repository lyupro/skillforge-mcp (2 stars, last pushed 23d ago), licensed MIT. It adds 25 tokens to every session and 419 once invoked, about $0.0001 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-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-notes
A release-note generator that turns Git history and referenced issues into release notes following the Keep a Changelog format.
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.
Changelog Generator
Generate release notes from git commits, updates, or feature lists.
Release Engineering
Semantic versioning, changelog generation, and release/hotfix management so releases are predictable and reversible.