What is bump-version?

A command that updates a plugin's version number across its configuration files and changelog. Major, minor, and patch are standard version-increase levels that signal the size of a change.

Use it when releasing a plugin update, choosing a major, minor, or patch bump, and previewing the proposed file changes with a dry run.

It prevents related files from carrying different version numbers and shows the exact changes before they are applied.

bump-version — Command for Claude Code by davistroy

Install

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.

Clone the repo

git clone --depth 1 https://github.com/davistroy/claude-marketplace

Made for: Claude Code.

Or install personal-plugin, the plugin that ships this one along with the rest of its 29 skills, 23 commands, 10 agents, 2 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/davistroy/claude-marketplace/bump-version/github.svg)](https://agentmods.dev/commands/davistroy/claude-marketplace/bump-version)

Your own site

<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/bump-version"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/bump-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/bump-version"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/bump-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,019 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00012	$0.02019
Opus 5	$0.00006	$0.01009
Sonnet 5	$0.00002	$0.00404
Haiku 4.5	$0.00001	$0.00202

Measured 10d ago against content hash 3e23487f0667, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

bump-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 10d 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.

plugins/personal-plugin/commands/bump-version.md · 297 lines

How it starts

The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bump Version Command

Automate version updates across all plugin configuration files. This command ensures version numbers stay synchronized between plugin.json, marketplace.json, and CHANGELOG.md.

Input Validation

Required Arguments:

<plugin-name> - Name of the plugin to version (must match a subdirectory in plugins/ that contains .claude-plugin/plugin.json)
<bump-type> - Type of version bump: major, minor, or patch

Optional Arguments:

--dry-run - Preview version changes without modifying any files

Dry-Run Mode: When --dry-run is specified:

Show current version and calculated new version
Show which files would be modified with their proposed changes
Show the diff that would be applied to each file
Prefix all output with [DRY-RUN] to clearly indicate preview mode
Do NOT write any changes to disk
Skip the commit prompt (nothing to commit in dry-run)

Validation: If arguments are missing or invalid, display:

Usage: /bump-version <plugin-name> <major|minor|patch>

Examples:
  /bump-version personal-plugin minor    # 1.6.0 -> 1.7.0
  /bump-version bpmn-plugin patch        # 1.5.0 -> 1.5.1
  /bump-version personal-plugin major    # 1.6.0 -> 2.0.0

Available plugins:
  [Scan the plugins/ directory for subdirectories containing .claude-plugin/plugin.json.
   List each discovered plugin name.]

If plugin-name is not found, display:

Error: Plugin '[name]' not found.

Available plugins:
  [Scan the plugins/ directory for subdirectories containing .claude-plugin/plugin.json.
   List each discovered plugin name.]

Check the plugins/ directory for valid plugin names.

Plugin Discovery: Use the Glob tool to scan plugins/*/.claude-plugin/plugin.json. Each match yields a valid plugin name from the directory path. If no plugins are found, report: "Error: No plugins found in the plugins/ directory."

If bump-type is invalid, display:

Error: Invalid bump type '[type]'.

Valid bump types:
  - major  (breaking changes)      1.0.0 -> 2.0.0
  - minor  (new features)          1.0.0 -> 1.1.0
  - patch  (bug fixes)             1.0.0 -> 1.0.1

Read the full file on GitHub · 297 lines

Changes

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.

10d ago First seen · 297 lines · 12 tokens per session scan A 3e23487f0667

Subscribe to this mod's changes

bump-version is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 2,019 once invoked, about $0.0001 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-31.

Git and workflow Releases

land

Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).

gmickel/flow-next · 25 tokens

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.

OpenHands/extensions · 44 tokens

ship

Ship is the operational release-prep flow for a connected project repo.

robotaitai/project-bedrock · 0 tokens

release-plan

A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.

alisunstar/OpenSunstar · 0 tokens

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.

dsswift/ion · 28 tokens

release

Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.

terrene-foundation/kailash-coc-claude-py · 0 tokens