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/sequenzia/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/sequenzia/claude-plugins/bump-plugin-version)<a href="https://agentmods.dev/commands/sequenzia/claude-plugins/bump-plugin-version"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/bump-plugin-version/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/sequenzia/claude-plugins/bump-plugin-version"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/bump-plugin-version.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.00010 | $0.00901 |
| Opus 5.5 | $0.00004 | $0.00360 |
| Sonnet 5.5 | $0.00002 | $0.00180 |
| Haiku 4.5 | $0.00001 | $0.00090 |
Grade A, and why
bump-plugin-version 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Version Bumper
Bump the version of any plugin in this repository. This command discovers available plugins, prompts for the bump level, and updates both the plugin configuration and marketplace metadata.
Workflow
Execute these steps in order.
Step 1: Discover Available Plugins
Find all plugins in this repository:
# List plugin directories
ls -d plugins/*/
For each discovered plugin directory, read its plugin.json:
- Path:
plugins/{plugin_name}/.claude-plugin/plugin.json - Extract the
nameandversionfields
Build a list of plugins with their current versions for display to the user.
Step 2: Select Plugin
Use AskUserQuestion to prompt the user to select a plugin.
Display each plugin as an option with its current version:
- Format: "{plugin_name} (v{current_version})"
- Example: "task-manager (v0.1.0)"
Step 3: Select Bump Level
Use AskUserQuestion to ask which version component to bump.
Options:
- patch - Bug fixes and minor changes (0.1.0 → 0.1.1)
- minor - New features, backwards compatible (0.1.0 → 0.2.0)
- major - Breaking changes (0.1.0 → 1.0.0)
Step 4: Calculate New Version
Parse the current version string (format: MAJOR.MINOR.PATCH).
Apply the bump:
- patch: Increment PATCH, keep MAJOR and MINOR
- Example: 1.2.3 → 1.2.4
- minor: Increment MINOR, reset PATCH to 0, keep MAJOR
- Example: 1.2.3 → 1.3.0
- major: Increment MAJOR, reset MINOR and PATCH to 0
- Example: 1.2.3 → 2.0.0
Step 5: Confirm Version Change
Use AskUserQuestion to confirm the version bump.
Display:
Plugin: {plugin_name}
Current version: {current_version}
New version: {new_version}
Bump type: {bump_level}
Proceed with this version change?
Options:
- "Confirm" - Proceed with the update
- "Cancel" - Abort the operation
If user selects "Cancel", stop and report: "Version bump cancelled."
Step 6: Update Plugin Configuration
Edit the plugin's configuration file:
- Path:
plugins/{plugin_name}/.claude-plugin/plugin.json - Update the
versionfield to the new version
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 · 152 lines · 10 tokens per session scan A 3828ebef1bcc
bump-plugin-version is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 901 once invoked, about $0.0000 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.
ship
Ship is the operational release-prep flow for a connected project repo.