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.
curl -O https://raw.githubusercontent.com/sangvucitek/MCP_SAP/main/.claude/commands/celebrate.mdgit clone --depth 1 https://github.com/sangvucitek/MCP_SAPWrote 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/sangvucitek/mcp_sap/celebrate)<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.
<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>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 | $0.00000 | $0.00320 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
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 10d 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.
This is a copy
100% identical to celebrate — 0 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.
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
)"
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.
- 10d ago First seen · 109 lines · 0 tokens per session scan A 7d3eeb4d0eea
celebrate is a command published in the GitHub repository sangvucitek/MCP_SAP (0 stars, last pushed 4mo 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 0 lines, and is treated as a copy.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.