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/release-checknpx skills add floor/vlist --skill release-checkgit clone --depth 1 https://github.com/floor/vlistWhat 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.00022 | $0.00509 |
| Opus 5 | $0.00011 | $0.00254 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 69 lines · 22 tokens per session scan A a74514839252
release-check is a skill published in the GitHub repository floor/vlist (16 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 509 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
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
version-management
Guide to managing and promoting theme versions in WP Rig.
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.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
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.