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.
npx agentmods add commands/xiaolai/claudepot-app/bumpgit clone --depth 1 https://github.com/xiaolai/claudepot-appWrote 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/claudepot-app/bump)<a href="https://agentmods.dev/commands/xiaolai/claudepot-app/bump"><img src="https://agentmods.dev/badge/commands/xiaolai/claudepot-app/bump.svg" alt="Measured on agentmods" 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 | $0.00071 | $0.03998 |
| Opus 5 | $0.00036 | $0.01999 |
| Sonnet 5 | $0.00014 | $0.00800 |
| Haiku 4.5 | $0.00007 | $0.00400 |
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 5d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump version
Bump Claudepot's version in every file that holds one. Version lives in five sources of truth:
| File | Line | Notes |
|---|---|---|
Cargo.toml |
top-level [workspace.package] version = "X.Y.Z" |
Feeds every Rust crate via version.workspace = true |
package.json |
"version": "X.Y.Z" |
Frontend build stamp |
src-tauri/tauri.conf.json |
"version": "X.Y.Z" |
Shown to the OS (menu bar "About", bundle metadata) |
README.md |
> **Status: {stage}** (\X.Y.Z`).` line |
Public-facing status banner — the first thing visitors see in the repo |
web/src/app/(reader)/app/install/page.mdx |
> **Status: {stage} (\X.Y.Z`).**` line |
Public-facing status banner on claudepot.com/app/install — same shape, different file (mind the dot placement) |
All five MUST match byte-for-byte. A mismatch produces a release with a wrong "About" dialog, bundles that refuse to install over previous versions, a README that lies about the current stage, or a website that quotes a version 10 releases old.
Two more files ride along in the same commit:
| File | Why |
|---|---|
CHANGELOG.md |
Stubbed in Step 4 |
Cargo.lock |
Derived, but committed. It stamps each workspace crate's own version, so a bump changes it (8 lines at v0.3.2 — four crates × two fields). Nothing edits it by hand; cargo check regenerates it. It is still part of the release commit — verify with git show --stat v0.3.2. |
Seven files total. Leaving Cargo.lock out is the easy miss: the
bump appears complete, then the next cargo command rewrites it and
leaves main dirty for whoever pulls next.
Inputs
$ARGUMENTS must be one of:
patch— bump the last segment (0.0.2→0.0.3)minor— bump the middle segment, zero the last (0.0.2→0.1.0)major— bump the first segment, zero the rest (0.1.0→1.0.0)- An explicit
X.Y.Zstring — used verbatim beta— start or advance a prerelease cycle (see "Beta path" below)- An explicit
X.Y.Z-beta.Nstring — used verbatim (the beta path)
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.
- 5d ago First seen · 349 lines · 71 tokens per session scan A 91085ea8bf0e
bump is a command published in the GitHub repository xiaolai/claudepot-app (118 stars, last pushed today), licensed ISC. It adds 71 tokens to every session and 3,998 once invoked, about $0.0004 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.
Other commands, from other repositories
celebrate
You are celebrating a project milestone! Follow these steps to create a new release.
minor-version-update
Update documentation for minor version releases (0.4.x).
release-version-bump
Workflow command scaffold for release-version-bump in claude-terminal.
release
Создать релиз фреймворка Claude Code Starter.
Rollback
回滚到上一个稳定版本.
gsd:complete-milestone
Archive completed milestone and prepare for next version.