Borrowing it
Nothing to install: this file belongs to princeton-ddss/blackfish. 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/princeton-ddss/blackfish/main/.claude/commands/release-checklist.mdgit clone --depth 1 https://github.com/princeton-ddss/blackfishWrote 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/commands/princeton-ddss/blackfish/release-checklist)<a href="https://agentmods.dev/commands/princeton-ddss/blackfish/release-checklist"><img src="https://agentmods.dev/badge/commands/princeton-ddss/blackfish/release-checklist.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.1 | $0.00000 | $0.00278 |
| Opus 5 | $0.00000 | $0.00139 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
release-checklist 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 6d 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
Output the release checklist for preparing a new version release.
Release Checklist
Before releasing a new version, ensure you have completed the following:
Pre-Release
- All PRs for this release are merged to main
- CI is green on main branch
Version Bump
- Update version in
lib/pyproject.toml - Update version in
web/package.json(keep in sync)
Testing
- Full test suite passes
- Python:
cd lib && uv run just test - Frontend:
cd web && npm test
- Python:
- Update coverage badge:
cd lib && uv run coverage - Manual smoke test of key features
Documentation
- README reflects current functionality
- Images table updated if new service images added
- Models table updated if new models tested
Release
- Create release commit:
git commit -m "Release vX.Y.Z" - Tag the release:
git tag vX.Y.Z - Push with tags:
git push && git push --tags - Create GitHub release with release notes
- Verify PyPI package published (if automated)
Post-Release
- Announce release if significant changes
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.
- 6d ago First seen · 36 lines · 0 tokens per session scan A 2334ac62502c
release-checklist is a command published in the GitHub repository princeton-ddss/blackfish (24 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 278 tokens. 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 commands, from other repositories
speckit.spex.finish
Smoke test + squash + merge/keep (land the code on main).
4-close-project
Name: 4-close-project Purpose: Apply an OpenSpec change through TDD, verify it, prepare or update the PR, and leave archive for after merge.
explore-release
This legacy command is a rename notice only. Its workflow is now rpi-explore-release.
FinishQa
Release sign-off — verifies all TC outcomes recorded, no P0/P1 defects open, drafts plain-language release notes. Transitions ADO to Done.
publish-gate
Pre-publish smoke verification — pack, install into a tmpdir, run the configured smoke command, assert expected output. Catches the "code worked locally but the published tarball is broken" class of bug.
qa-ship
Run Phase 5 QA validation, acceptance testing, and release preparation.