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/release-check/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/release-check)<a href="https://agentmods.dev/skills/floor/vlist/release-check"><img src="https://agentmods.dev/badge/skills/floor/vlist/release-check/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/release-check"><img src="https://agentmods.dev/badge/skills/floor/vlist/release-check.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.00022 | $0.00509 |
| Opus 5.5 | $0.00009 | $0.00204 |
| Sonnet 5.5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
release-check 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
Pre-Release Checklist
Run all checks needed before publishing a new vlist release.
Context
- Current version: !
node -p "require('./package.json').version" - Latest tag: !
git describe --tags --abbrev=0 2>/dev/null || echo "none" - Unreleased commits: !
git log $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~10")..HEAD --oneline --no-merges 2>/dev/null | head -20
Instructions
Run each check and report results. Do NOT fix issues — just report them.
1. Version
- If
$ARGUMENTSprovides a target version, check thatpackage.jsonmatches - Check that the version follows semver
- Based on commits since last tag, suggest whether this should be patch/minor/major
2. Changelog
- Check if CHANGELOG.md has an entry for the target version
- If not, flag it as missing
3. Typecheck
- Run
bun run typecheck - Report pass/fail
4. Tests
- Run
bun test - Report pass/fail with counts
5. Build
- Run
bun run build - Report pass/fail
6. Size
- Run
bun run size - Report gzipped sizes
- Flag any regressions if previous sizes are known
7. Git State
- Check for uncommitted changes
- Check that branch is up to date with remote
Output
## Release Checklist: vX.Y.Z
| Check | Status | Notes |
|-------|--------|-------|
| Version | ✅/❌ | ... |
| Changelog | ✅/❌ | ... |
| Typecheck | ✅/❌ | ... |
| Tests | ✅/❌ | N passed |
| Build | ✅/❌ | ... |
| Size | ✅/❌ | core: X.XKB |
| Git state | ✅/❌ | ... |
**Ready to publish** / **Blocked — N issues to resolve**
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 · 69 lines · 22 tokens per session scan A a74514839252
release-check is a skill published in the GitHub repository floor/vlist (18 stars, last pushed 9d ago), licensed MIT. It adds 22 tokens to every session and 509 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
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.
release-gate-loop
A release check that tests a change, reports whether it passes, and can run a limited fix-and-retest cycle. A release is the act of making a software version available.
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
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.