Borrowing it
Nothing to install: this file belongs to floor/vlist. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/floor/vlist/main/.claude/skills/changelog/SKILL.mdgit clone --depth 1 https://github.com/floor/vlistWrote 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/floor/vlist/changelog)<a href="https://agentmods.dev/skills/floor/vlist/changelog"><img src="https://agentmods.dev/badge/skills/floor/vlist/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/floor/vlist/changelog"><img src="https://agentmods.dev/badge/skills/floor/vlist/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.00017 | $0.00365 |
| Opus 5.5 | $0.00007 | $0.00146 |
| Sonnet 5.5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
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.
What it actually says
Generate Changelog Entry
Generate a changelog entry for the vlist project based on recent commits.
Context
- Latest tag: !
git describe --tags --abbrev=0 2>/dev/null || echo "no tags" - Recent commits since last tag: !
git log $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEAD --oneline --no-merges 2>/dev/null || git log --oneline -20
Instructions
- If
$ARGUMENTSis provided, use it as the base ref. Otherwise use the latest tag (shown above). - Categorize commits using conventional commit types:
- Added —
featcommits - Changed —
refactor,perfcommits - Fixed —
fixcommits - Testing —
testcommits - Other —
docs,chore,stylecommits
- Added —
- Output a markdown changelog entry in this format:
## [version] — YYYY-MM-DD
### Added
- Description (scope)
### Changed
- Description (scope)
### Fixed
- Description (scope)
- Omit empty categories. Use the scope from commit messages in parentheses.
- Write clear, user-facing descriptions — reword commit messages if needed for clarity.
- Do NOT write the entry to any file — just output it for review.
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 · 44 lines · 17 tokens per session scan A e45619fe6e9d
changelog is a skill published in the GitHub repository floor/vlist (18 stars, last pushed 9d ago), licensed MIT. It adds 17 tokens to every session and 365 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
create-draft-pr
Create a draft pull request for the current session. Use when the user wants to open a draft PR with the session's changes.
create-pr
Create a pull request for the current session. Use when the user wants to open a PR with the session's changes.
release-process
Pre-release validation, npm publish procedures, and post-publish verification.
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.