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/and3r817/dot-claude-plugins/bump-versiongit clone --depth 1 https://github.com/and3r817/dot-claude-pluginsWrote 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/and3r817/dot-claude-plugins/bump-version)<a href="https://agentmods.dev/commands/and3r817/dot-claude-plugins/bump-version"><img src="https://agentmods.dev/badge/commands/and3r817/dot-claude-plugins/bump-version.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.1 | $0.00018 | $0.01137 |
| Opus 5 | $0.00009 | $0.00568 |
| Sonnet 5 | $0.00004 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
bump-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 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTEXT
Git status: !git status --short
Changed plugins: !
git status --short | grep -E "plugin\.json|SKILL\.md|scripts/|hooks/" | cut -d'/' -f1 | sort -u | head -20
INSTRUCTIONS
${1:?Error: Plugin name required. Usage: /bump-version <plugin-name|all> [major|minor|patch|auto]}
Version Bump: $1
Bump type: ${2:-auto}
SEMVER DECISION MATRIX
Use this matrix to determine appropriate version bump:
MAJOR (X.0.0) — Breaking Changes
| Trigger | Example |
|---|---|
| Complete rewrite | SKILL.md structure changed |
| Incompatible API changes | Hook contract changed |
| Remove documented behavior | Removed allowed-tools |
| Drop runtime/platform support | Changed Python version requirement |
MINOR (x.Y.0) — New Features, Backward Compatible
| Trigger | Example |
|---|---|
| New capability added | Added Bash(sg:*) to allowed-tools |
| Content removal (notable) | Removed documentation section |
| Behavior config change | Model version updated |
| Functionality deprecated | Marked feature for removal |
| New reference files | Added new reference docs |
PATCH (x.y.Z) — Fixes, No Functional Changes
| Trigger | Example |
|---|---|
| Metadata additions | Added homepage/repository |
| Internal restructuring | Moved references to skills/ |
| Formatting changes | Multi-line to single line |
| Typo/doc fixes | Fixed spelling |
| Bug fixes | Fixed script logic |
PROCESS
Step 1: Identify Target Plugins
If $1 is "all":
- Find all plugins with changes using git status
- List plugins with modified plugin.json or SKILL.md
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 · 180 lines · 18 tokens per session scan A 52693409ff5a
bump-version is a command published in the GitHub repository and3r817/dot-claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 18 tokens to every session and 1,137 once invoked, about $0.0001 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
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
version-bump
Bump versions across the monorepo during release process.
gen-goreleaser
Generate GoReleaser configuration with multi-arch Docker builds and release automation.
create-pr
Create a draft GitHub PR from the current feature branch.
configure
Configure which Fizzy.do board to sync todos to.
sync
Manually trigger todo sync to Fizzy.do.