A release checklist command for preparing a software project milestone. It gathers release details, checks tests and repository contents, updates documentation, builds the project, and creates a Git release tag.

Use it when preparing a versioned release to run tests, check for uncommitted changes and exposed credentials, update project files, build all platforms, and push commits and tags.

It puts common release checks and publishing steps in one repeatable process, reducing the chance of missing a test, build, documentation update, or tag.

How oisee/vibing-steampunk configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to oisee/vibing-steampunk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/oisee/vibing-steampunk/main/.claude/commands/celebrate.md

Clone the repo

git clone --depth 1 https://github.com/oisee/vibing-steampunk

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/oisee/vibing-steampunk/celebrate/github.svg)](https://agentmods.dev/commands/oisee/vibing-steampunk/celebrate)

Your own site

<a href="https://agentmods.dev/commands/oisee/vibing-steampunk/celebrate"><img src="https://agentmods.dev/badge/commands/oisee/vibing-steampunk/celebrate/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/oisee/vibing-steampunk/celebrate"><img src="https://agentmods.dev/badge/commands/oisee/vibing-steampunk/celebrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,434 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.02434
Opus 5.5	$0.00000	$0.00974
Sonnet 5.5	$0.00000	$0.00487
Haiku 4.5	$0.00000	$0.00243

Measured 1mo ago against content hash 841bbe56274a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

celebrate 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

celebrate — 100% identical, 208 lines differ

.claude/commands/celebrate.md · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Celebrate Milestone Release

You are celebrating a project milestone. Releases are cut by CI: push the tag, .github/workflows/release.yml does the rest, and you check what it did. The manual path at the end is the fallback for when CI cannot run.

Why CI, in one paragraph: every manual release so far has had to be checked by hand for the same things. v2.58.0 almost shipped six binaries of the previous release (build-all builds three platforms). A binary built before the tag says v2.57.0-25-g977f968. v2.58.0 and v2.59.0 went out without LICENSE/NOTICE. v2.59.0's binaries record a Go VCS stamp of a modified checkout of another branch, not the tag. The workflow builds from a clean checkout of the tag and refuses all of those, by reading the files instead of trusting exit codes.

1. Gather Release Information

Ask the user for:

Version number (e.g., v2.60.0) — suggest based on changes (major/minor/patch)
Release title (e.g., "only what you saw") — it goes into the tag message
Key highlights — they go into the README, which becomes the release notes

2. Release-prep PR (everything the tag should contain)

On a branch, in one PR:

README.md "What's New": add ### vX.Y.Z — new since vA.B.C (and, if any, ### vX.Y.Z — behaviour changes since vA.B.C). Every ### vX.Y.Z … section there becomes the release notes, verbatim. Without one, CI falls back to git-cliff's commit list and warns.
CHANGELOG.md: git-cliff --tag vX.Y.Z -o CHANGELOG.md (git-cliff 2.12.0, uvx git-cliff works). CI no longer pushes this to main after the fact, so it lands here, reviewed, and inside the tag.
README/CLAUDE.md version references, if any.

Before merging: go test ./..., and the leak scan runs in CI on the PR.

3. Tag and push the tag

After the PR is merged, on an up-to-date main:

git switch main && git pull --ff-only
git tag -a vX.Y.Z -m "Release vX.Y.Z: <title>"
git push origin vX.Y.Z

The tag subject after vX.Y.Z: becomes the release title (vX.Y.Z: <title>). Push only the tag; CI pushes nothing anywhere.

Read the full file on GitHub · 177 lines

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.

1mo ago Changed · +40 lines 841bbe56274a
1mo ago Changed · +28 lines 6e17ae8815c2
2mo ago First seen · 109 lines · 0 tokens per session scan A 7d3eeb4d0eea

Subscribe to this mod's changes

celebrate is a command published in the GitHub repository oisee/vibing-steampunk (522 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,434 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-08-30.

Git and workflow Releases abap adt mcp vibe-coding

celebrate next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
celebrateoisee/vibing-steampunk	Command	522	15d ago	MIT	A	0	Claude Code
release-updatemodu-ai/moai-adk	Command	1.3k	3d ago	Apache-2.0	A	32	Claude Code
releasemodu-ai/moai-adk	Command	1.3k	3d ago	Apache-2.0	A	59	Claude Code
releasealexeykrol/claude-code-starter	Command	196	29d ago	none	A	12	Claude Code
landgmickel/flow-next	Command	717	yesterday	MIT	A	13	Claude Code
qualityDesko77/claude-code-skills-1c	Command	90	yesterday	MIT	A	18	Claude Code
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code

vibing-steampunk: Command for Claude Code