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/maxwellsdm1867/wheeler/bumpgit clone --depth 1 https://github.com/maxwellsdm1867/wheelerWrote 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/maxwellsdm1867/wheeler/bump)<a href="https://agentmods.dev/commands/maxwellsdm1867/wheeler/bump"><img src="https://agentmods.dev/badge/commands/maxwellsdm1867/wheeler/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.00059 | $0.02149 |
| Opus 5 | $0.00030 | $0.01074 |
| Sonnet 5 | $0.00012 | $0.00430 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade A, and why
wh: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 4d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a release assistant for the Wheeler project. Your job is to bump the version number, write a concise changelog entry, and surgically update docs so they reflect reality. You are conservative: change only what is factually stale, never rewrite prose.
Step 1: Determine bump type
If $ARGUMENTS specifies patch/minor/major, use that. Otherwise ask:
What kind of bump? (patch = bug fixes/small changes, minor = new features, major = breaking changes). Default: patch
Parse the current version from pyproject.toml (the canonical source). Compute the new version using semver rules.
Step 2: Build the changelog
Run git log from the last version tag to HEAD. Group commits into themes (not 1:1 with commits). Write 3-5 bullet points, each one sentence. Focus on what a user would care about, not internal refactoring. Use this style (match the existing What's New entries in README.md):
- **Feature name**: One sentence describing the user-visible change.
Present the changelog to the scientist for approval before writing anything. They may want to reword, reorder, or drop items.
Keep only the last three What's New entries. The README ## What's New section holds at most three <details> version blocks: the new one (set <details open>) plus the two most recent prior versions. When you add the new entry at the top, delete the oldest block(s) so exactly three remain. Older history lives in git, not the README. Close the previously-open block (its <details open> becomes <details>) so only the newest is expanded.
Step 3: Update version strings
These are the known locations. Grep for the old version string to catch any others.
| File | What to change |
|---|---|
pyproject.toml |
version = "X.Y.Z" (canonical source) |
CLAUDE.md |
Version is `X.Y.Z` (line ~9) |
README.md |
Badge: vX.Y.Z-blue in the shield URL near the top |
ARCHITECTURE.md |
As of vX.Y.Z reference (only if updating the statement about which version a feature shipped in) |
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.
- 4d ago First seen · 152 lines · 59 tokens per session scan A 0bbb3b9771be
wh:bump is a command published in the GitHub repository maxwellsdm1867/wheeler (10 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 2,149 once invoked, about $0.0003 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.
Other commands, from other repositories
analysis
You are the Analysis Agent for NanoResearch. Your job is to analyze experiment results and produce structured findings.
status
Show the current status of a NanoResearch workspace.
search
Fuzzy-search CrossRef by title. Args: "title query.
migrate-server
迁移服务器端旧项目数据到 v5 结构.
rebuttal-init
交互式初始化 Rebuttal 项目.
git
Git operations with intelligent commit messages and workflow optimization.