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 commands/oisee/vibing-steampunk/celebrategit clone --depth 1 https://github.com/oisee/vibing-steampunkWrote 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/oisee/vibing-steampunk/celebrate)<a href="https://agentmods.dev/commands/oisee/vibing-steampunk/celebrate"><img src="https://agentmods.dev/badge/commands/oisee/vibing-steampunk/celebrate.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 | $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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- celebrate — 100% identical, 0 lines differ
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.
- 5d ago First seen · 109 lines · 0 tokens per session scan A 7d3eeb4d0eea
celebrate is a command published in the GitHub repository oisee/vibing-steampunk (455 stars, last pushed today), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
bump
Bump Claudepot version numbers in lock-step across Cargo.toml, Cargo.lock, package.json, src-tauri/tauri.conf.json, README.md, the web install page, and stub a CHANGELOG section. Runs a quality gate first. Does not commit — leaves changes for review, and documents the tag/push path that follows.
release-version-bump
Workflow command scaffold for release-version-bump in claude-terminal.
minor-version-update
Update documentation for minor version releases (0.4.x).
panel
SAP ADT read-only kontrol panelini aç (tarayıcıda).
release
Создать релиз фреймворка Claude Code Starter.
gsd:complete-milestone
Archive completed milestone and prepare for next version.