Borrowing it
Nothing to install: this file belongs to henkisdabro/Claude-Code-MCP-Server-Selector. 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/henkisdabro/Claude-Code-MCP-Server-Selector/main/.claude/skills/version-bump/SKILL.mdgit clone --depth 1 https://github.com/henkisdabro/Claude-Code-MCP-Server-SelectorWrote 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/henkisdabro/claude-code-mcp-server-selector/version-bump)<a href="https://agentmods.dev/skills/henkisdabro/claude-code-mcp-server-selector/version-bump"><img src="https://agentmods.dev/badge/skills/henkisdabro/claude-code-mcp-server-selector/version-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/skills/henkisdabro/claude-code-mcp-server-selector/version-bump"><img src="https://agentmods.dev/badge/skills/henkisdabro/claude-code-mcp-server-selector/version-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.00030 | $0.01067 |
| Opus 5.5 | $0.00012 | $0.00427 |
| Sonnet 5.5 | $0.00006 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
version-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 2mo 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Bump Skill
Updates semantic version consistently across all project files. This skill handles version updates only - use /release for the full release workflow including git and npm publishing.
Trigger Words
Use when user says: "bump version", "update version", "version bump", or when called by the release skill.
Version Locations (Canonical List)
These are ALL locations where version numbers appear. Every bump MUST update all of these:
Primary Sources
| File | Line | Pattern | Example |
|---|---|---|---|
package.json |
3 | "version": "X.Y.Z" |
"version": "2.1.0" |
src/cli/index.ts |
18 | const VERSION = 'X.Y.Z'; |
const VERSION = '2.1.0'; |
Documentation
| File | Line | Pattern | Example |
|---|---|---|---|
README.md |
12 | > **vX.Y.Z**: |
> **v2.1.0**: |
docs/index.html |
45 | "softwareVersion": "X.Y.Z" |
"softwareVersion": "2.1.0" |
Auto-generated (DO NOT edit manually)
| File | Notes |
|---|---|
package-lock.json |
Updated by npm install --package-lock-only |
Procedure
Step 1: Determine New Version
Ask user or determine from context:
| Type | Pattern | When to Use |
|---|---|---|
| patch | X.Y.Z+1 | Bug fixes, minor changes |
| minor | X.Y+1.0 | New features, backwards compatible |
| major | X+1.0.0 | Breaking changes |
Or accept explicit version like "2.1.0".
Step 2: Read Current Version
node -p "require('./package.json').version"
Step 3: Update All Locations (IN ORDER)
-
package.json (line 3):
"version": "NEW_VERSION", -
src/cli/index.ts (line 18):
const VERSION = 'NEW_VERSION'; -
README.md (line 12):
> **vNEW_VERSION**: [brief description of changes] -
docs/index.html (line 45):
"softwareVersion": "NEW_VERSION",
Step 4: Update Lock File
npm install --package-lock-only
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.
- 2mo ago First seen · 156 lines · 30 tokens per session scan A f2e8c77b0c53
version-bump is a skill published in the GitHub repository henkisdabro/Claude-Code-MCP-Server-Selector (8 stars, last pushed 13d ago), licensed MIT. It adds 30 tokens to every session and 1,067 once invoked, about $0.0001 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-31.
Other skills, from other repositories
write-release-notes
Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes…
macos-release
Release a native macOS app to GitHub with DMG packaging and Sparkle appcast updates. Use this skill whenever the user wants to publish a new version, create a release, ship an update, push a release to GitHub, or update the appcast. Also trigger when the user mentions DMG creation, Sparkle signing, notarization…
npm-release
Guide for setting up automated npm package releases via GitHub Actions using Trusted Publishing (OIDC). Use when creating release workflows, publishing to npm, or troubleshooting CI/CD publish failures.
gitlab-cli
Reference guide for GitLab CLI (glab) commands. Use when running glab commands for issues, merge requests, pipelines, releases, or CI/CD operations, or when the user asks about GitLab CLI syntax.
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.