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 skills/a/claude-booping/releasenpx skills add A/claude-booping --skill releasegit clone --depth 1 https://github.com/A/claude-boopingWhat 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.00056 | $0.01545 |
| Opus 5 | $0.00028 | $0.00772 |
| Sonnet 5 | $0.00011 | $0.00309 |
| Haiku 4.5 | $0.00006 | $0.00154 |
Grade A, and why
release 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release — cut a booping plugin release
Releases the booping plugin from a release/X.Y.Z branch: verifies the version, drafts public release notes, merges to master, tags vX.Y.Z, and publishes the GitHub release.
Run from the repo root with the release/X.Y.Z branch checked out. Default branch is master. Version is single-source in .claude-plugin/plugin.json.
Preflight — gather facts
Run these read-only; report the resolved values back before doing anything that writes:
git rev-parse --abbrev-ref HEAD # current branch — expect release/X.Y.Z
jq -r .version .claude-plugin/plugin.json # the version to ship
gh release list --limit 1 # last published release
git status --porcelain # working tree must be clean
git remote # remote name — this repo uses `gh`, NOT origin
Resolve: VERSION (from plugin.json), TAG = v$VERSION, LAST_TAG (newest existing v* tag), BRANCH, and REMOTE (the single remote — do not assume origin; use whatever git remote reports). Substitute $REMOTE into every push/fetch/log-range below.
Phase 0 — Verify version + previous release
Gate every check; if any fails, stop and report — do not proceed to merge.
- Clean tree —
git status --porcelainis empty. Dirty tree → stop. - On the release branch —
BRANCHisrelease/$VERSION. If it ismasteror a mismatchedrelease/*, stop and ask the user to switch. - Version bumped —
$VERSIONis strictly greater thanLAST_TAG(semver). The bump commit follows the conventionchore(booping): bump plugin version <prev> → $VERSION; confirm it exists ingit log master..HEAD. If plugin.json still equalsLAST_TAG, stop — the bump is missing. - Tag is free —
git tag -l "$TAG"andgh release view "$TAG"both return nothing. An existing tag/release → stop (already released). - Branch is ahead of master — fetch first (
git fetch $REMOTE), thengit log $REMOTE/master..HEAD --onelineis non-empty (there is something to release).
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.
- 2d ago First seen · 119 lines · 56 tokens per session scan A 16b479c401a3
release is a skill published in the GitHub repository A/claude-booping (14 stars, last pushed 17d ago), licensed MIT. It adds 56 tokens to every session and 1,545 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
tutti-app-release
Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
document-release
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/AGENTS.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs".…