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 skills add A/claude-booping --skill releasegit clone --depth 1 https://github.com/A/claude-boopingWrote 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/skills/a/claude-booping/release)<a href="https://agentmods.dev/skills/a/claude-booping/release"><img src="https://agentmods.dev/badge/skills/a/claude-booping/release/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/skills/a/claude-booping/release"><img src="https://agentmods.dev/badge/skills/a/claude-booping/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.01545 |
| Opus 5.5 | $0.00022 | $0.00618 |
| Sonnet 5.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 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.
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.
- 1mo 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 yesterday), licensed MIT. It adds 56 tokens to every session and 1,545 once invoked, about $0.0002 per session on Opus 5.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
pdlc-ship
A software release workflow that runs tests, updates the version and change log, creates a Git tag, and starts CI/CD, the automated build and deployment process.
pdlc-changelog
A changelog updater that reads recent Git commits and records user-facing changes in a service or application’s CHANGELOG.md. A changelog is a history of additions, fixes, and other notable changes.
log-changes
Use before creating, drafting, editing, or reviewing changelog entries (CHANGELOG.md or the project's equivalent), including when this is a subtask of implementing a feature, fixing a bug, or preparing a release and the user did not explicitly ask for this skill. Also use for requests to 'document this change' or 'add…
vibe-changelog
Generates and maintains two changelog files from git tags, TASKS.md, DECISIONS.md, and feature folders. CHANGELOG.md at repo root is developer-facing in Keep a Changelog format with task IDs and decisions. CHANGELOGCLIENT.md is plain English, grouped by "what you can now do", written like a product update — no task…
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.