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 cwinvestments/memstack --skill changelog-generatorgit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/cwinvestments/memstack/changelog-generator)<a href="https://agentmods.dev/skills/cwinvestments/memstack/changelog-generator"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/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/cwinvestments/memstack/changelog-generator"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/changelog-generator.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.00063 | $0.01105 |
| Opus 5.5 | $0.00025 | $0.00442 |
| Sonnet 5.5 | $0.00013 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
memstack-development-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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generator: Generating changelog...
Produces a formatted CHANGELOG.md from git commit history, grouped by type and ready for release.
Activation
| Trigger | Status |
|---|---|
| User says "generate changelog" or "update changelog" | ACTIVE |
| User says "what changed" or "release notes" | ACTIVE |
| User says "write changelog" or "changelog since" | ACTIVE |
| User wants to view git log only | NOT this skill: use git commands directly |
| User wants a diary entry | NOT this skill: use Diary |
Context Guard
- Do NOT use for session logging (that's Diary)
- Do NOT use for commit message writing (that's a git workflow)
- Do NOT use for PR descriptions (that's a git workflow)
- This skill ONLY produces CHANGELOG.md content from existing commits
Steps
Step 1: Determine the range
Ask the user or infer from context:
| Parameter | Default | Example |
|---|---|---|
| Since tag/date | Last tag or last 7 days | v3.3.0, 2026-03-01 |
| Until | HEAD | v3.4.0, HEAD |
| Format | Keep a Changelog | Conventional, custom |
# Find the last tag
git describe --tags --abbrev=0 2>/dev/null || echo "No tags found"
# Get commits since last tag (or date)
git log --oneline --no-merges $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~50")..HEAD
Step 2: Categorize commits
Parse each commit message and classify by prefix:
| Prefix | Category | Changelog Section |
|---|---|---|
feat: / feature: |
Features | ### Added |
fix: / bugfix: |
Bug Fixes | ### Fixed |
docs: |
Documentation | ### Changed |
refactor: |
Refactoring | ### Changed |
perf: |
Performance | ### Changed |
test: |
Tests | (omit unless user requests) |
chore: / build: / ci: |
Maintenance | (omit unless user requests) |
BREAKING CHANGE or !: |
Breaking | ### Breaking Changes |
| No prefix | Uncategorized | ### Other |
Step 3: Generate the changelog entry
Follow Keep a Changelog format:
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.
- 1mo ago Changed b8e7c12ebcf3
- 1mo ago First seen · 135 lines · 63 tokens per session scan A ab5dd8029d8f
memstack-development-changelog-generator is a skill published in the GitHub repository cwinvestments/memstack (425 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,105 once invoked, about $0.0003 per session on Opus 5.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
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…
gitflow
Branching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches, feature/release/hotfix branches, semantic versioning, and pull request rules. Use when creating a branch, naming a branch, planning a release or hotfix, writing a commit message, or setting up branch…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.