Borrowing it
Nothing to install: this file belongs to QuantumBFS/sci-brain. 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/QuantumBFS/sci-brain/main/.claude/skills/bump-version/SKILL.mdgit clone --depth 1 https://github.com/QuantumBFS/sci-brainWrote 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/skills/quantumbfs/sci-brain/bump-version)<a href="https://agentmods.dev/skills/quantumbfs/sci-brain/bump-version"><img src="https://agentmods.dev/badge/skills/quantumbfs/sci-brain/bump-version/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/skills/quantumbfs/sci-brain/bump-version"><img src="https://agentmods.dev/badge/skills/quantumbfs/sci-brain/bump-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.01430 |
| Opus 5.5 | $0.00030 | $0.00572 |
| Sonnet 5.5 | $0.00015 | $0.00286 |
| Haiku 4.5 | $0.00007 | $0.00143 |
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 1mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Version
Overview
sci-brain is a Claude Code plugin. Its version is declared in three JSON files that must stay in lockstep — the marketplace reads it from marketplace.json, plugin tooling reads it from plugin.json, and npm/pi read it from package.json. CI (scripts/validate_skills.py) fails if they diverge, and .github/workflows/publish.yml refuses to publish unless the pushed tag equals v + package.json's version. A release is: bump all three files → commit → annotated tag → push → GitHub release.
Version Source of Truth
| File | Path to version |
|---|---|
.claude-plugin/plugin.json |
.version |
.claude-plugin/marketplace.json |
.plugins[0].version |
package.json |
.version |
All three MUST match. If they diverge, CI's version-sync check fails, the npm publish tag gate rejects the release, and the marketplace and the installed plugin report different versions.
When to Use
- "tag a version", "bump version", "cut a release", "release v0.x"
- After a batch of merged PRs that warrants a new release
- Before announcing changes that downstream users need to pull
Do NOT use for:
- Pre-release / draft tags (the workflow below assumes a real release)
- Hotfix to an old branch — this skill assumes you tag from
main
Bump Type → New Version
Read current version from .claude-plugin/plugin.json, then:
- patch (
X.Y.Z→X.Y.Z+1): bugfix, doc tweak, no behavior change - minor (
X.Y.Z→X.Y+1.0): new skill, new feature, additive change - major (
X.Y.Z→X+1.0.0): breaking change to a skill's contract / removed skill
If the user didn't specify, ask which bump type (patch/minor/major) before continuing.
Procedure
-
Read current version from
.claude-plugin/plugin.jsonand confirmmarketplace.jsonandpackage.jsonmatch. If they already disagree, stop and flag it — don't paper over the drift. -
Edit all three files to the new version. Use the
Edittool, notsed, so the diff is reviewable.
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.
- 1mo ago First seen · 103 lines · 75 tokens per session scan A 9861f54531c6
bump-version is a skill published in the GitHub repository QuantumBFS/sci-brain (101 stars, last pushed 23d ago), licensed MIT. It adds 75 tokens to every session and 1,430 once invoked, about $0.0003 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.