Borrowing it
Nothing to install: this file belongs to pandazki/pneuma-skills. 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/pandazki/pneuma-skills/main/.claude/commands/bump.mdgit clone --depth 1 https://github.com/pandazki/pneuma-skillsWrote 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/pandazki/pneuma-skills/bump)<a href="https://agentmods.dev/commands/pandazki/pneuma-skills/bump"><img src="https://agentmods.dev/badge/commands/pandazki/pneuma-skills/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/pandazki/pneuma-skills/bump"><img src="https://agentmods.dev/badge/commands/pandazki/pneuma-skills/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.00000 | $0.02217 |
| Opus 5 | $0.00000 | $0.01108 |
| Sonnet 5 | $0.00000 | $0.00443 |
| Haiku 4.5 | $0.00000 | $0.00222 |
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 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bump — Version Bump & Release
Perform a full version bump: sync main, write changelog, refresh top-level docs, bump version, and push.
Steps
1. Sync main
git checkout main && git pull origin main
If the working tree is dirty, stop and ask the user to resolve it first.
2. Determine version bump
Review all commits since the last version tag to decide the bump level per Semantic Versioning:
- patch (x.y.Z): bug fixes, minor improvements, doc updates
- minor (x.Y.0): new features, new modes, new API endpoints, new viewer capabilities
- major (X.0.0): breaking changes to contracts, CLI interface, or manifest format
Read the current version from package.json. Compute the new version. If unsure, ask the user.
3. Write CHANGELOG entry
Read CHANGELOG.md and the git log since the last version bump commit. Write a new version section at the top following the existing format:
## [X.Y.Z] - YYYY-MM-DD
### Added
- ...
### Fixed
- ...
### Improved
- ...
Rules:
- Group changes by category (Added / Fixed / Improved / Changed / Removed)
- Each bullet should be a concise, user-facing description — not a commit message copy
- Bold the feature name, then describe what it does
- Omit categories with no entries
- Do NOT include chore/CI/version-bump commits
4. Refresh top-level docs
Review README.md and AGENTS.md against the current codebase state. Fix any contradictions, outdated info, or missing features. This is a holistic review, not just appending — trim stale content, update tables, fix version numbers.
AGENTS.mdis the single source of agent instructions;CLAUDE.mdis a one-line@AGENTS.mdimport — never write content into it.
Specifically check:
AGENTS.md**Version:**line → update to new versionAGENTS.md**Builtin Modes:**list → matchescore/mode-loader.tsregistrationsAGENTS.mdtech stack table → matchespackage.jsondependenciesAGENTS.mdproject structure tree → reflects any new/moved directoriesAGENTS.mdserver API reference → includes any new endpoints.claude/rules/*.md→ add any newly discovered gotchas to the matching domain rule, remove resolved onesREADME.mdmode table → matches manifest descriptionsREADME.mdCLI help section → matches actual CLI outputREADME.mdfeature list / roadmap → reflects current state
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 Changed · +5 lines a82b0db88892
- 11d ago First seen · 191 lines · 0 tokens per session scan A 0e4c43778f98
bump is a command published in the GitHub repository pandazki/pneuma-skills (160 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,217 tokens. 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
release
Generate changelog, bump version, and create git tag.
cancel-ship
Cancel active ship pipeline.
aw-upgrade
Upgrade gh-aw extension, recompile and validate all workflows, and open a PR with changes.
bump
Bump the app version or build number across all targets in the current project.
aw-merge
Merge develop branch to main with PR, CI check, and squash merge.
release
Bump version, tag, push, and create a GitHub release with auto-generated notes.