Borrowing it
Nothing to install: this file belongs to xiaolai/vmark. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/xiaolai/vmark/main/.claude/commands/bump.mdgit clone --depth 1 https://github.com/xiaolai/vmarkWrote 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/xiaolai/vmark/bump)<a href="https://agentmods.dev/commands/xiaolai/vmark/bump"><img src="https://agentmods.dev/badge/commands/xiaolai/vmark/bump/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/xiaolai/vmark/bump"><img src="https://agentmods.dev/badge/commands/xiaolai/vmark/bump.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.00023 | $0.01736 |
| Opus 5.5 | $0.00009 | $0.00694 |
| Sonnet 5.5 | $0.00005 | $0.00347 |
| Haiku 4.5 | $0.00002 | $0.00174 |
Grade A, and why
bump 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 11d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Bump
Bump the version number across all 5 required files, write the release notes in
CHANGELOG.md, land the commit on main
through a pull request, then tag and push.
main cannot be pushed directly (since 2026-07-27 — enforce_admins: true
on the frontend + rust checks, see .claude/rules/60-ai-governance.md §10).
A direct push of the bump commit is rejected, because the required checks cannot
have run on a commit the remote has never seen. Tag pushes are not gated, so
the release trigger is unchanged.
Input
$ARGUMENTS
Phase 1: Determine New Version
Read current version from package.json.
Parse $ARGUMENTS:
| Input | Action |
|---|---|
0.5.0 |
Use exactly as specified |
patch |
Increment patch: 0.4.2 → 0.4.3 |
minor |
Increment minor: 0.4.2 → 0.5.0 |
major |
Increment major: 0.4.2 → 1.0.0 |
| (empty) | Default to patch |
Validate the resolved version matches ^[0-9]+\.[0-9]+\.[0-9]+$. Anything
else (e.g., 0.7.14.1, 0.7, v0.7.15) is rejected — the Tauri updater
parses latest.json.version with semver and rejects non-canonical
shapes, and any divergence between the five files breaks the build.
Display: Current: {old} → New: {new} and ask user to confirm.
Phase 2: Quality Gate
Run pnpm check:all before touching any version file. Abort the bump
on any failure — tagging a broken build creates a public tag that the
release workflow then fails on, and the tag stays in the repo until
manually deleted.
Phase 3: Update All 5 Files
All five files must be updated — see .claude/rules/40-version-bump.md.
| File | Field |
|---|---|
package.json |
"version" |
src-tauri/tauri.conf.json |
"version" |
src-tauri/Cargo.toml |
version |
server/mcp/package.json |
"version" |
server/mcp/src/cli.ts |
const VERSION |
Use the Edit tool for each file — not sed.
Then sync the derived lockfile, which is a sixth file in the commit even though nothing edits it by hand:
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.
- 11d ago Changed · +5 lines e108706b41ba
- 25d ago Changed · +18 lines · +5 tokens per session 7f252c223ee2
- 2mo ago First seen · 138 lines · 18 tokens per session scan A 961b6ba50c0d
bump is a command published in the GitHub repository xiaolai/vmark (878 stars, last pushed yesterday), licensed ISC. It adds 23 tokens to every session and 1,736 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.
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.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
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.
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.