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 qwerfunch/cladding --skill changeloggit clone --depth 1 https://github.com/qwerfunch/claddingWrote 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/qwerfunch/cladding/changelog)<a href="https://agentmods.dev/skills/qwerfunch/cladding/changelog"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/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/qwerfunch/cladding/changelog"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/changelog.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.00121 | $0.00704 |
| Opus 5.5 | $0.00048 | $0.00282 |
| Sonnet 5.5 | $0.00024 | $0.00141 |
| Haiku 4.5 | $0.00012 | $0.00070 |
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 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cladding changelog — release notes from the spec
The spec is the SSoT, so "what shipped?" is collected, never recalled. clad changelog turns
<since>..HEAD into a deterministic manifest: feature shards classified (added-as-done /
flipped-to-done / modified-while-done / archived), grouped by capability (plus an
uncategorized bucket — itself a drift signal), the spec inventory diff, and conventional
feat:/fix: commits that name no feature id (work that shipped outside the spec — report it
honestly, don't hide it).
Protocol
- Collect. Run
clad changelog --json --since <ref>(omit--sinceto use the latest tag; if the repo has no tags the command says so — ask the user for a ref). - Render EN + KO release notes from the manifest, in the CHANGELOG.md house style:
- Open with a
**In one line:**abstract (what a user gains, one breath). - Group by the manifest's capability groups; use user-impact verbs ("the gate now runs your entry point"), not implementation verbs ("refactored stage runner").
- No
F-…/AC-…ids in prose (Soft Shell policy) — ids belong to the audit surface only. - Source every claim from the manifest — a feature
titleor anacceptance[]sentence. Never invent a change, never embellish beyond what an AC states. If the manifest is empty, say "no shipped changes since " — that line is the honest deliverable. - Put
unsharded_commitsunder an "Also changed" section, marked as not yet spec-tracked.
- Open with a
- Audit asks ("show verification", "어디까지 검증됐어?") → print
clad changelog --audit --since <ref>verbatim — that table keeps ids and marks every verification ref resolved ✓ / unresolved ✗ (a ✗ is spec-annotation drift worth reporting). - Catalog asks ("what does this project do, in full?") →
clad changelog --catalogprints the whole capability → feature → acceptance listing of the living spec.
clad changelog # markdown since the latest tag (deterministic fallback)
clad changelog --json --since v0.5.2 # the manifest you render notes from
clad changelog --audit --since v0.5.2
clad changelog --catalog
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 First seen · 39 lines · 121 tokens per session scan A 520ee59cdbbd
changelog is a skill published in the GitHub repository qwerfunch/cladding (16 stars, last pushed 1mo ago), licensed MIT. It adds 121 tokens to every session and 704 once invoked, about $0.0005 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
release-docs
Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.
ccc-rollback
Roll production back by picking a known-good commit or tag, creating atomic git revert commits, pushing them, redeploying through the $ccc-deploy runners, and verifying health. Use when a deploy is bad, production is broken, or the user asks to revert or roll back a release.
changelog
Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.
ship
Fully automated ship workflow. Merges the base branch, runs tests, audits coverage, reviews the diff, generates a CHANGELOG entry, bumps the version, commits, pushes, and creates the PR. Use when asked to "ship", "create a PR", or "open a pull request".
git-flow
Use when creating a branch, using worktrees for parallel work, committing, or wrapping up. Covers branch naming, conventional commits, short-lived branches, worktree isolation, and final merge/cleanup.
changelog-manager
Reviews git history and updates CHANGELOG.md with entries for [Unreleased] section (converted from agent).