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/reggiechan74/cc-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/reggiechan74/cc-plugins/version-bump)<a href="https://agentmods.dev/commands/reggiechan74/cc-plugins/version-bump"><img src="https://agentmods.dev/badge/commands/reggiechan74/cc-plugins/version-bump/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/reggiechan74/cc-plugins/version-bump"><img src="https://agentmods.dev/badge/commands/reggiechan74/cc-plugins/version-bump.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.00019 | $0.00751 |
| Opus 5.5 | $0.00008 | $0.00300 |
| Sonnet 5.5 | $0.00004 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
version-bump 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Bump
Bump a plugin's version consistently across all files that reference it.
Arguments received: $ARGUMENTS
Instructions
Step 1: Parse Arguments
Extract <plugin-name> and <new-version> from the arguments.
- If no arguments provided, ask: "Which plugin and what version? (e.g.,
math-paper-creator 0.5.0)" - If only plugin name provided, read current version from its
plugin.jsonand suggest the next minor bump. Ask user to confirm or specify a different version. - Validate the version follows semver (X.Y.Z).
Step 2: Locate Files
Find all files that need updating for the given plugin:
- Plugin manifest:
<plugin-dir>/.claude-plugin/plugin.json— the"version"field - README badge:
<plugin-dir>/README.md— the shields.io version badge between<!-- badges-start -->and<!-- badges-end --> - Marketplace registry:
.claude-plugin/marketplace.json— the"version"field for this plugin's entry - Changelog:
<plugin-dir>/CHANGELOG.md— add a new## [X.Y.Z] - YYYY-MM-DDsection
If any file doesn't exist, note it and skip (e.g., some plugins may not have a CHANGELOG).
Step 3: Read Current State
Read each file and verify the current version. Report:
Current version: X.Y.Z
New version: A.B.C
Files to update:
- <plugin-dir>/.claude-plugin/plugin.json
- <plugin-dir>/README.md (badge)
- .claude-plugin/marketplace.json
- <plugin-dir>/CHANGELOG.md
Step 4: Update Versions
Update each file:
- plugin.json: Change
"version": "X.Y.Z"to"version": "A.B.C" - README.md: Change
version-X.Y.Z-bluetoversion-A.B.C-bluein the badge URL - marketplace.json: Change the version for this plugin's entry only (match by plugin name)
- CHANGELOG.md: If it exists, insert a new section at the top (after the header):
Leave the entries as placeholders for the user to fill in. If the user provided changelog notes in the arguments or conversation, populate them.## [A.B.C] - YYYY-MM-DD ### Added - ### 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 First seen · 93 lines · 19 tokens per session scan A 83028993a99e
version-bump is a command published in the GitHub repository reggiechan74/cc-plugins (7 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 751 once invoked, about $0.0001 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
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or 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.
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-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.