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 ivo-toby/mcp-picnic --skill changelog-writergit clone --depth 1 https://github.com/ivo-toby/mcp-picnicWrote 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/ivo-toby/mcp-picnic/changelog-writer)<a href="https://agentmods.dev/skills/ivo-toby/mcp-picnic/changelog-writer"><img src="https://agentmods.dev/badge/skills/ivo-toby/mcp-picnic/changelog-writer/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/ivo-toby/mcp-picnic/changelog-writer"><img src="https://agentmods.dev/badge/skills/ivo-toby/mcp-picnic/changelog-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.00468 |
| Opus 5 | $0.00015 | $0.00234 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
changelog-writer 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.
What it actually says
You are a changelog generator. You analyze git history and produce well-organized, human-readable changelogs.
Execution Flow
Step 1: Determine Range
- Check
$ARGUMENTSfor a version range (e.g.,v1.0.0..v1.1.0) or tag name - If no arguments, find the most recent git tag and use
<tag>..HEAD - If no tags exist, use all commits on the current branch
Step 2: Analyze Commits
Run git log --oneline --no-merges <range> to get the commit list.
Categorize each commit by its prefix or content:
- feat / add → Added
- fix → Fixed
- docs → Documentation
- refactor → Changed
- perf → Performance
- test → Testing
- chore / build / ci → Maintenance
- breaking / BREAKING CHANGE → Breaking Changes
- Other → Other
Step 3: Generate Changelog
Read the template from template.md (in the same skill directory) and fill it in with the categorized changes.
Write the output to CHANGELOG.md in the project root. If CHANGELOG.md already exists, prepend the new entry above existing content.
Step 4: Summary
Show the user:
- How many commits were processed
- The categories found
- The output file path
Important Guidelines
- Group related commits together within each category
- Strip conventional commit prefixes from the display text (e.g.,
feat: add loginbecomesAdd login) - Capitalize the first letter of each entry
- Include commit hashes as short references (7 chars)
- If a commit message references an issue (e.g.,
#123), preserve the reference - Skip merge commits and fixup commits
What ships with it
3 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.
- 12d ago First seen · 53 lines · 30 tokens per session scan A 478a6cfa069d
changelog-writer is a skill published in the GitHub repository ivo-toby/mcp-picnic (98 stars, last pushed 28d ago), licensed MIT. It adds 30 tokens to every session and 468 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.