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 jnMetaCode/skillet --skill changeloggit clone --depth 1 https://github.com/jnMetaCode/skilletWrote 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/jnmetacode/skillet/changelog)<a href="https://agentmods.dev/skills/jnmetacode/skillet/changelog"><img src="https://agentmods.dev/badge/skills/jnmetacode/skillet/changelog/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/jnmetacode/skillet/changelog"><img src="https://agentmods.dev/badge/skills/jnmetacode/skillet/changelog.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.00039 | $0.00503 |
| Opus 5 | $0.00019 | $0.00251 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
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 9d 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
changelog
A changelog is for users deciding whether to upgrade, not a commit dump. Format: Keep a Changelog + semver sections.
Procedure
-
Find the range. Last release tag:
git describe --tags --abbrev=0. Collect commits since:git log <tag>..HEAD --oneline --no-merges. -
Bucket each commit:
Added(feat) ·Fixed(fix) ·Changed(behavior changes, perf)Deprecated·Removed·Security- Drop pure
chore/ci/test/docsnoise unless user-visible.
-
Rewrite each line user-first. Translate implementation into impact:
- commit:
fix(ingest): treat mtime regressions as edits - entry:
Fixed duplicate chunks after restoring files from backup.One line each; link the PR/issue number when the repo uses them.
- commit:
-
Squash threads. Five commits iterating on one feature = one entry.
-
Pick the version bump from the buckets: breaking → major, Added → minor, only Fixed → patch (pre-1.0: breaking → minor).
-
Write the section at the top of
CHANGELOG.md:## [0.2.0] - 2026-06-10 ### Added - Live re-indexing: `engram watch` picks up edits automatically. ### Fixed - Duplicate chunks after restoring files from backup. -
Keep an
## [Unreleased]section at the very top for changes landing between releases; releasing = renaming it and starting a fresh one.
Quality bar
Every entry answers: what can I do now / what stopped being broken? If an entry needs the source code to make sense, rewrite it.
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.
- 9d ago First seen · 46 lines · 39 tokens per session scan A 52ab2e0c3b7c
changelog is a skill published in the GitHub repository jnMetaCode/skillet (1 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 503 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-31.
Other skills, from other repositories
release-management
Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
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.
Release Engineering
Semantic versioning, changelog generation, and release/hotfix management so releases are predictable and reversible.
release-deploy
Release and deploy via GitHub tags and GitHub Actions (not every commit). Creates production releases from main and beta releases from staging using the GitHub CLI. Use when the user asks to release, ship, deploy, cut a version, tag a release, publish beta/production, create a GitHub Release, or bump a semver tag. On…
release-manager
A release-management tool for calculating semantic versions, generating changelogs and release notes, creating tags, and preparing releases. Semantic versioning uses version numbers to describe the scale of changes.