A release checklist for a Go project that guides the steps from milestone information through tests, documentation, builds, commits, and GitHub release tags.

Preparing release notes, checking the repository, testing and linting, building platform binaries, committing changes, and creating a Git tag.

It reduces the chance of forgetting validation, security checks, platform builds, or release metadata before publishing a version.

How sangvucitek/MCP_SAP configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to sangvucitek/MCP_SAP. 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/sangvucitek/MCP_SAP/main/.claude/commands/celebrate.md

Clone the repo

git clone --depth 1 https://github.com/sangvucitek/MCP_SAP

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/sangvucitek/mcp_sap/celebrate/github.svg)](https://agentmods.dev/commands/sangvucitek/mcp_sap/celebrate)

Your own site

<a href="https://agentmods.dev/commands/sangvucitek/mcp_sap/celebrate"><img src="https://agentmods.dev/badge/commands/sangvucitek/mcp_sap/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/sangvucitek/mcp_sap/celebrate"><img src="https://agentmods.dev/badge/commands/sangvucitek/mcp_sap/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 640 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 100% copy Near-identical to another mod 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.00640
Opus 5.5	$0.00000	$0.00256
Sonnet 5.5	$0.00000	$0.00128
Haiku 4.5	$0.00000	$0.00064

Measured 2mo ago against content hash 7d3eeb4d0eea, 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 2mo 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

This is a copy

100% identical to celebrate — 208 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/celebrate.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 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! Follow these steps to create a new release:

1. Gather Release Information

Ask the user for:

Version number (e.g., v1.2.0) - suggest based on changes (major/minor/patch)
Release title (e.g., "CLI & Cookie Authentication")
Key highlights to include in release notes

2. Pre-Release Checklist

Run these checks and report results:

# Run all unit tests
go test ./...

# Check for uncommitted changes
git status

# Verify no credentials in repo
git log --all -p | grep -E "password|PASSWORD|secret|SECRET" | head -5 || echo "No credentials found"

3. Update Documentation

If needed, update:

README.md - version references, feature list
CLAUDE.md - project status metrics
reports/vsp-status.md - if exists

4. Commit & Push

# Stage and commit any pending changes
git add -A
git commit -m "Prepare release vX.Y.Z"

# Push to origin
git push origin main

5. Build All Platforms

make build-all

Verify all 9 binaries are created in build/ directory.

6. Create Git Tag

git tag -a vX.Y.Z -m "Release vX.Y.Z: <title>"
git push origin vX.Y.Z

7. Create GitHub Release

Use gh release create with:

All binaries from build/
Release notes highlighting key features
Mark as latest release

gh release create vX.Y.Z \
  build/vsp-linux-amd64 \
  build/vsp-linux-arm64 \
  build/vsp-linux-386 \
  build/vsp-linux-arm \
  build/vsp-darwin-amd64 \
  build/vsp-darwin-arm64 \
  build/vsp-windows-amd64.exe \
  build/vsp-windows-arm64.exe \
  build/vsp-windows-386.exe \
  --title "vX.Y.Z: <title>" \
  --notes "$(cat <<'NOTES'
## What's New

- Feature 1
- Feature 2

## Downloads

| Platform | Architecture | File |
|----------|--------------|------|
| Linux | x64 | vsp-linux-amd64 |
| Linux | ARM64 | vsp-linux-arm64 |
| macOS | x64 | vsp-darwin-amd64 |
| macOS | Apple Silicon | vsp-darwin-arm64 |
| Windows | x64 | vsp-windows-amd64.exe |

## Installation

Download the appropriate binary, make it executable, and add to your PATH.

## Full Changelog

See commits since last release.
NOTES
)"

Read the full file on GitHub · 109 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.

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 sangvucitek/MCP_SAP (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 640 tokens. A static security scan graded it A with 0 findings. It is 100% identical to celebrate, differing in 208 lines, and is treated as a copy.

Git and workflow Releases

celebrate next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
celebratesangvucitek/MCP_SAP	Command	0	6mo ago	MIT	A	0	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
release-managerruvnet/agentic-flow	Command	838	yesterday	none	A	0	Claude Code
create-prdsswift/ion	Command	5	yesterday	MIT	A	28	Claude Code
rally-merge-prddgonzal3/rally	Command	6	3d ago	MIT	A	0	Claude Code

MCP_SAP: Command for Claude Code