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 tasanakorn/cc-marketplace --skill changeloggit clone --depth 1 https://github.com/tasanakorn/cc-marketplaceWrote 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/tasanakorn/cc-marketplace/changelog)<a href="https://agentmods.dev/skills/tasanakorn/cc-marketplace/changelog"><img src="https://agentmods.dev/badge/skills/tasanakorn/cc-marketplace/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/tasanakorn/cc-marketplace/changelog"><img src="https://agentmods.dev/badge/skills/tasanakorn/cc-marketplace/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.00049 | $0.00787 |
| Opus 5 | $0.00024 | $0.00394 |
| Sonnet 5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
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 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Skill
Generate CHANGELOG.md entries from git history using Keep a Changelog format.
Capabilities
- Read existing CHANGELOG.md and detect where to insert new entries
- Analyze git history since last recorded commit
- Filter out noise commits (changelog-only, config-only changes)
- Review actual diffs to write accurate, user-facing descriptions
- Group changes into standard sections: Added, Changed, Fixed, Removed
Usage
This skill activates when:
- User asks to "update the changelog"
- User asks to "generate changelog entries"
- User wants to "add recent changes to CHANGELOG.md"
- User mentions "changelog" in context of git history
Approach
Step 1: Read Current State
Read CHANGELOG.md in the project root. Extract the last recorded commit hash from the first ## ... \hash`` header line.
- If CHANGELOG.md does not exist, create one with a title and description header
- If no hash is found in any header, fall back to the repository's initial commit
Step 2: Get New Commits
Run:
git log <LAST_HASH>..HEAD --format="%h %s" --reverse
If there are no new commits, inform the user and stop.
Step 3: Filter Noise Commits
Skip commits that ONLY touch:
CHANGELOG.mdCLAUDE.mdor.claude/files.gitignore- Dev config files (editor settings, linter configs) with no functional code changes
Step 4: Review Diffs
For each remaining commit, review the actual diff:
git diff <HASH>^..<HASH>
Diffs are the source of truth — do not rely solely on commit messages.
Step 5: Group and Write Entries
Group changes into sections (omit empty ones):
- Added — New features or capabilities
- Changed — Modifications to existing functionality
- Fixed — Bug fixes
- Removed — Removed features or capabilities
Merge related commits into single bullets. Write concise, user-facing descriptions. Reference the git hash each entry covers through.
Step 6: Format Header
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 · 114 lines · 49 tokens per session scan A c49452c24179
changelog is a skill published in the GitHub repository tasanakorn/cc-marketplace (2 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 787 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
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.