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 sigistry/marketplace --skill changelog-assemblygit clone --depth 1 https://github.com/sigistry/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/sigistry/marketplace/changelog-assembly)<a href="https://agentmods.dev/skills/sigistry/marketplace/changelog-assembly"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/changelog-assembly/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/sigistry/marketplace/changelog-assembly"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/changelog-assembly.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.00070 | $0.00891 |
| Opus 5 | $0.00035 | $0.00445 |
| Sonnet 5 | $0.00014 | $0.00178 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
changelog-assembly 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 8d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Assembly
Purpose
Provide a consistent, repeatable methodology for converting raw git history, whether or not it follows Conventional Commits, into release notes and changelog entries that a human reader actually benefits from. Covers classification, grouping, de-duplication, audience-appropriate phrasing, linking, and the Unreleased section. Tech-agnostic.
The assembly pipeline
- Collect the commit range (
<last-tag>..HEAD, or an explicit range). Exclude merge commits from the entry list; mine them only for PR numbers. - Classify each commit into a Keep a Changelog category. If the message is conventional, map the type; if not, infer from the diff.
- De-duplicate & fold: collapse "fix typo", "wip", and follow-up commits into the logical change they belong to.
- Rephrase each surviving item into user-facing language: describe the observable effect, not the code mechanics.
- Order by category (Added, Changed, Deprecated, Removed, Fixed, Security) and by impact within each.
- Elevate breaking changes into a prominent callout at the top.
- Link PR/issue references and add compare links.
Category mapping
| Conventional type | Keep a Changelog category | Notes |
|---|---|---|
feat |
Added | New capability |
fix |
Fixed | Bug fix |
perf |
Changed | Behavior/characteristics changed |
refactor |
usually omitted | Internal; include only if user-observable |
docs/test/ci/build/chore |
usually omitted | Internal unless user-facing |
any ! / BREAKING CHANGE: |
Changed/Removed + top callout | Always surfaced |
| dependency CVE bump | Security | Even if labeled chore/build |
Inferring type from non-conventional history
When the message is uninformative, read the diff:
| Diff signal | Category |
|---|---|
| New files / new public exports / new endpoints / new flags | Added |
| Deleted exports / endpoints / flags / files | Removed |
@deprecated markers, deprecation notices |
Deprecated |
| Changed defaults, signatures, output shape | Changed |
| Bug-fix pattern (guard added, off-by-one, null check) | Fixed |
| Auth hardening, input sanitization, dependency vuln bump | Security |
What ships with it
2 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.
- 8d ago First seen · 64 lines · 70 tokens per session scan A e6edd204e78c
changelog-assembly is a skill published in the GitHub repository sigistry/marketplace (3 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 891 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
git-for-research-code
When the user wants to version-control optimization research code - small commits per experiment change, tags for paper result snapshots, .gitignore for solver logs, linking result tables to commit hashes, and branch strategy for risky refactors. Also use when the user mentions "git workflow," "version control…
last-tag
Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.
version-bump
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.
commit-push-pr
Full git workflow - creates branch, commits, pushes, and creates or updates a PR with summary and test plan.
commit
Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.
git-branchless
Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.