kit: Command for Claude Code

.claude/commands/update-version.md

update-version is a command for Claude Code from hamsurang/kit. It costs 14 tokens per session (327 once invoked), scanned A, original, MIT.

A command that updates semantic version numbers, which communicate whether a software change is breaking, additive, or a fix. It compares plugin changes with the main branch and updates the marketplace version too.

In plain words
What is it for?
Finding changed plugin directories, choosing major, minor, or patch updates from the differences, changing each plugin's JSON manifest, and updating the marketplace manifest without committing.
Why use it?
It removes the need to inspect every changed plugin and calculate version increases manually, reducing inconsistent release metadata.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions .claude-plugin.

This is hamsurang/kit's own configuration. It tells Claude Code how to work on kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to hamsurang/kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hamsurang/kit/main/.claude/commands/update-version.md
Clone the repo
git clone --depth 1 https://github.com/hamsurang/kit

Made for: Claude Code.

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.

agentmods badge for update-version

README.md
[![agentmods](https://agentmods.dev/badge/commands/hamsurang/kit/update-version/github.svg)](https://agentmods.dev/commands/hamsurang/kit/update-version)
Your own site
<a href="https://agentmods.dev/commands/hamsurang/kit/update-version"><img src="https://agentmods.dev/badge/commands/hamsurang/kit/update-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.

agentmods 80×15 button for update-version

Your own site · 80×15
<a href="https://agentmods.dev/commands/hamsurang/kit/update-version"><img src="https://agentmods.dev/badge/commands/hamsurang/kit/update-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 327 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00327
Opus 5.5 $0.00006 $0.00131
Sonnet 5.5 $0.00003 $0.00065
Haiku 4.5 $0.00001 $0.00033

Measured 1mo ago against content hash 43f5d45d5c61, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.claude/commands/update-version.md · 32 lines

What it actually says

Context

  • Changed files vs main: !git diff --name-only origin/main...HEAD
  • Current marketplace.json: !cat .claude-plugin/marketplace.json

Your task

  1. Find changed plugins Parse the changed files list. For each unique plugins/<name>/ directory, that plugin needs a version bump.

  2. For each changed plugin:

    • Read plugins/<name>/.claude-plugin/plugin.json
    • Get the diff for that plugin: git diff origin/main...HEAD -- plugins/<name>/
    • Determine bump type:
      • major: skill or command file removed/renamed, breaking behavior change
      • minor: new command, skill, or agent file added
      • patch: content edits, docs, bug fixes, refactoring
    • Bump version in plugin.json using semver (e.g. 1.0.0 → 1.0.1 for patch)
  3. Bump marketplace version in .claude-plugin/marketplace.json:

    • Take the highest bump type across all changed plugins
    • Apply that bump to the current marketplace version field
  4. Report all changes: list each plugin and old→new version, and marketplace old→new version.

Do NOT commit. Only update the JSON files.

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. 1mo ago First seen · 32 lines · 14 tokens per session scan A 43f5d45d5c61

Subscribe to this mod's changes

update-version is a command published in the GitHub repository hamsurang/kit (19 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 327 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-30.