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.
git clone --depth 1 https://github.com/PrabhdeepSingh/claude-pluginsWrote 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/prabhdeepsingh/claude-plugins/release)<a href="https://agentmods.dev/commands/prabhdeepsingh/claude-plugins/release"><img src="https://agentmods.dev/badge/commands/prabhdeepsingh/claude-plugins/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/commands/prabhdeepsingh/claude-plugins/release"><img src="https://agentmods.dev/badge/commands/prabhdeepsingh/claude-plugins/release.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.00059 | $0.01725 |
| Opus 5.5 | $0.00024 | $0.00690 |
| Sonnet 5.5 | $0.00012 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00172 |
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release — the five-home sync, done right every time
Why this exists: installed copies of the plugin are pinned — a change on main reaches nobody until the version is bumped and users run /plugin marketplace update. And the plugin's description lives in five files that must move together. Both halves of that have failed before (two releases of marketplace drift; one behavior fix that never got a bump). This command is the procedure.
If $ARGUMENTS is tag, skip straight to Phase 5 (the PR already merged). Otherwise run Phases 1–4 in order.
Guard first. This command releases the claude-plugins repo itself:
[ -f .claude-plugin/marketplace.json ] && [ -d sonu/skills ] \
&& echo "OK: claude-plugins repo" || echo "STOP: not the claude-plugins repo"
Phase 1 — What changed, and what bump does it earn
git log $(git describe --tags --abbrev=0 2>/dev/null || echo origin/main)..HEAD --oneline
git diff origin/main --stat 2>/dev/null | tail -5
CURRENT=$(python3 -c "import json; print(json.load(open('sonu/.claude-plugin/plugin.json'))['version'])")
echo "current version: $CURRENT"
Pick the bump (from $ARGUMENTS if given — the text typed after the command; if that token appears literally or is empty, infer from the diff):
| Change | Bump |
|---|---|
| New skill or command added, or behavior of an existing one meaningfully changed | minor |
| Fix/clarification to existing component, docs, manifests | patch |
| Removed or renamed a component, or changed how users invoke things | major |
Any user-visible change gets a bump. "It's just a wording fix in ship.md" is a behavior change for the model executing it — that exact reasoning skipped a bump once and left every installed copy running the buggy text.
Phase 2 — The five homes, in order
Update each; the version appears in homes 1–2, the plugin description in homes 1–5 (sync the description text only if the component set or a component's pitch changed):
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 Changed · +15 lines 2d02e1d99c6f
- 1mo ago First seen · 81 lines · 59 tokens per session scan A dbcf50cbbacc
release is a command published in the GitHub repository PrabhdeepSingh/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,725 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-31.
Other commands, from other repositories
version-bump
Bump versions across the monorepo during release process.
release
Generate changelog, bump version, and create git tag.
release-notes
Assemble release notes / a changelog entry for a commit range, even from non-conventional history.
changelog-claude
Read the Claude Code changelog since the last run (plus the Claude Platform release notes for model changes), triage every entry against the global Claude Code setup, and apply the improvements the owner approves. Ledgered, so nothing is re-offered.
version-guard
Classify API-surface changes as breaking or non-breaking and recommend a semver bump.
ship
Complete PR workflow from commit to production with validation.