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 agentmods add skills/floor/vlist/changelognpx skills add floor/vlist --skill changeloggit 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.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00365 |
| Opus 5 | $0.00009 | $0.00182 |
| Sonnet 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 3d 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.
- 3d ago First seen · 44 lines · 17 tokens per session scan A e45619fe6e9d
changelog is a skill published in the GitHub repository floor/vlist (16 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 365 once invoked, about $0.0001 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-01.
Other skills, from other repositories
goshipit
Pre-launch codebase audit skill. Use this whenever someone is about to ship, deploy, launch, push to main/prod, or merge a release - even without "goshipit" explicitly. Trigger on: "is my app ready?", "can I deploy now?", "pre-deploy check", "review before launch", "is this production-ready?", "check my codebase"…
release
Skill "release" from mahmoud/lithoxyl, covering release lithoxyl, pre-flight checks, release steps, 1. determine the release version and 2. update version for release.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
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.
parquet-dev-ml
Search the Apache parquet-dev mailing list by downloading the raw monthly mbox archives from lists.apache.org and grepping them locally. Use whenever the user wants to find, read, or quote a thread on the Parquet dev list ([email protected]) — e.g. "search the parquet-dev ML", "find the thread about X on the…