bump-patch

A command that increases the patch part—the third number—of a software version by one, such as changing 0.3.2 to 0.3.3. It updates the version in the specified project files without committing the changes.

In plain words
What is it for?
Use it when releasing a backward-compatible bug fix or small maintenance update, and when the version must be kept consistent in pyproject.toml and cli.py.
Why use it?
It avoids manually finding and changing repeated version numbers, which can leave files inconsistent or introduce typing mistakes.

Command for Claude Code

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/ianphil/promptbin/bump-patch
Clone the repo
git clone --depth 1 https://github.com/ianphil/promptbin

Made for: Claude Code.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 167 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.00008 $0.00167
Opus 5 $0.00004 $0.00084
Sonnet 5 $0.00002 $0.00033
Haiku 4.5 $0.00001 $0.00017

Measured yesterday against content hash 9f3b235808b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bump-patch 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 yesterday.

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-patch.md · 23 lines

What it actually says

Bump Patch Version

Task

Increment the patch version (third number) by 1 in all relevant files.

Steps

  1. Find current version in pyproject.toml
  2. Parse the version (e.g., 0.3.2 -> major=0, minor=3, patch=2)
  3. Increment patch by 1 (e.g., 0.3.2 -> 0.3.3)
  4. Update version in:
    • pyproject.toml
    • cli.py
  5. Show the version change summary

Important

  • Only bump the patch version (x.y.Z)
  • Ensure all version references are updated consistently
  • Do NOT commit the changes automatically
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. yesterday First seen · 23 lines · 8 tokens per session scan A 9f3b235808b6

Subscribe to this mod's changes

bump-patch is a command published in the GitHub repository ianphil/promptbin (0 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 167 once invoked, about $0.0000 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.