agentmods.dev

bump-version

A command for changing plugin versions in plugin.json and marketplace.json, the files that describe a plugin and its marketplace listing.

In plain words
What is it for?
Use it to set a specific plugin version or automatically increase patch versions for plugins with updates.
Why use it?
It keeps both version records synchronized and can identify which plugins have changed since their last release.

Command for Claude Code

588 +1 22d ago A scan 10 tokens original MIT
View the source file FradSer/dotclaude
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.

agentmods
npx agentmods add commands/fradser/dotclaude/bump-version
Clone the repo
git clone --depth 1 https://github.com/FradSer/dotclaude

Made for: Claude Code.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00611
Opus 5 $0.00005 $0.00305
Sonnet 5 $0.00002 $0.00122
Haiku 4.5 $0.00001 $0.00061

Measured 3d ago against content hash 8a2656e90b2e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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.

.claude/commands/bump-version.md · 48 lines

How it starts

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

Atomically update <plugin-name>/.claude-plugin/plugin.json and .claude-plugin/marketplace.json to the same version.

Arguments: $ARGUMENTS — [plugin-name] [new-version]

  • no arguments: auto-increment patch for all plugins
  • plugin-name only: auto-increment patch for that plugin
  • plugin-name new-version: set explicit version for that plugin

Steps

No arguments — update only plugins with changes

  1. Read .claude-plugin/marketplace.json to get the full plugin list (all "name" entries).

  2. For each plugin, determine whether it has updates since its last release:

    • V = version in <PLUGIN>/.claude-plugin/plugin.json at HEAD
    • Walk git log --format=%H HEAD -- <PLUGIN>/.claude-plugin/plugin.json newest→oldest. The era of V starts at the first commit whose version != V; if every commit has version == V, the era starts at the plugin's creation commit (the oldest commit in the walk).
    • Has updates iff git diff --name-only <era-start>..HEAD -- <PLUGIN>/ shows any changed file other than <PLUGIN>/.claude-plugin/plugin.json — uncommitted working-tree changes (git diff --name-only HEAD -- <PLUGIN>/) count too.

  3. Bump patch only for plugins with updates (run the single-plugin flow for each); skip plugins without updates.

  4. Report: plugin: old → new for every updated plugin, and plugin: unchanged (skipped) for every skipped one.

Single plugin

  1. Parse $ARGUMENTS to extract PLUGIN and optional VERSION.

  2. Read current version from <PLUGIN>/.claude-plugin/plugin.json:

    python3 -c "import json; d=json.load(open('<PLUGIN>/.claude-plugin/plugin.json')); print(d['version'])"

  3. If VERSION not provided, compute patch increment:

    python3 -c "v='<current>'.split('.'); v[2]=str(int(v[2])+1); print('.'.join(v))"

  4. Edit <PLUGIN>/.claude-plugin/plugin.json — replace "version": "<current>" with "version": "<new>".

  5. Edit .claude-plugin/marketplace.json — find the entry where "name": "<PLUGIN>" and replace its "version" using the surrounding "name" line as context to target the correct entry.

Read the full file on GitHub · 48 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.

  1. 3d ago First seen · 48 lines · 10 tokens per session scan A 8a2656e90b2e

Subscribe to this mod's changes

bump-version is a command published in the GitHub repository FradSer/dotclaude (588 stars, last pushed 22d ago), licensed MIT. It adds 10 tokens to every session and 611 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-30.

Git and workflowReleasesclaude
Related

Other commands, from other repositories

review-renovate

Review and merge renovate PRs with automerge configuration updates.

liam-hq/liam · 11 tokens

release

Perform a full release: generate release notes, bump version, commit, tag, and push.

elirantutia/vibeyard · 0 tokens

release

Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.

swingerman/ha-dual-smart-thermostat · 29 tokens

SHIP_RELEASE

Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.

Osiris-DevWorks/smart-citizen · 34 tokens

release

This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.

Yeachan-Heo/oh-my-claudecode · 0 tokens

release

The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.

azrtydxb/procoder · 30 tokens