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 skills/lenoseibert/semver-plugin/bump-versionnpx skills add LenoSeibert/semver-plugin --skill bump-versiongit clone --depth 1 https://github.com/LenoSeibert/semver-pluginWrote 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/lenoseibert/semver-plugin/bump-version)<a href="https://agentmods.dev/skills/lenoseibert/semver-plugin/bump-version"><img src="https://agentmods.dev/badge/skills/lenoseibert/semver-plugin/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 | $0.00038 | $0.00526 |
| Opus 5 | $0.00019 | $0.00263 |
| Sonnet 5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00053 |
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 3d 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.
What it actually says
Bump the plugin version
Bump the semver-plugin version consistently across every file that carries it.
Arguments: $ARGUMENTS may be an explicit version (0.3.0) or a bump level
(major, minor, patch). If empty, decide the level yourself from the
uncommitted/unreleased changes and state your reasoning before writing.
Choosing the level
This repo is pre-1.0 and uses this policy:
- Breaking change to a published contract — hook event or command shape, skill
name/frontmatter, manifest keys, removal of a harness — bumps MINOR. - Everything else, including new features and docs-only changes, bumps PATCH.
- Every merge into
mainrequires a bump, docs-only included.
Inspect what actually changed before deciding: git diff main...HEAD --stat and
the diffs under skills/, hooks/, AGENTS.md, and the manifests.
Steps
-
Read the current version from
VERSION. -
Compute the new version. Strict SemVer, no leading
v, no leading zeroes. -
Write the identical version to all five files:
VERSION.codex-plugin/plugin.json.github/plugin/plugin.json.claude-plugin/plugin.jsongemini-extension.json
Keep JSON at 2-space indent with a trailing newline. Change only the
versionfield. -
Run
make validate-version(ornode scripts/check-version.js). It must printversion check passed: X.Y.Z. Fix any reported drift before going on. -
Run
make check-diffto catch whitespace errors. -
Commit exactly these five files with the message
chore(release): bump version to X.Y.Z— nothing else in the same commit.
Do not create the git tag and do not push to main. Tagging and the GitHub
Release are handled automatically by .github/workflows/release.yml once the
bump lands on main.
If the tag vX.Y.Z already exists on another commit, do not reuse it — a
released version is immutable. Bump again.
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.
- 3d ago First seen · 53 lines · 38 tokens per session scan A d5b9bd10f6d8
bump-version is a skill published in the GitHub repository LenoSeibert/semver-plugin (1 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 526 once invoked, about $0.0002 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 skills, from other repositories
helmor-release
Prepare Helmor releases by inspecting the current branch, drafting a concise user-facing Changesets entry first (bump + body — keep it as short as possible), creating any needed pending in-app release announcement under .announcements/, and then showing the user the result with a short menu of adjustments they can…
helmor-bump-vendors
Bump or upgrade the pinned versions of Helmor's bundled agent CLIs, SDKs, and supporting binaries — Claude Code + claude-agent-sdk (lockstep), Codex, Cursor SDK, OpenCode, Kimi, Pi, and gh / glab / cloudflared / llama.cpp / Node. Encodes exactly which files to edit (sidecar/package.json…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
github
GitHub CLI operations via gh for issues, PRs, Actions, releases, and REST/GraphQL API with --json/--jq parsing. Triggers on: "create an issue", "submit a PR", "check CI status", "why did CI fail", "merge a PR", or pasted GitHub URLs.
github-release-notes-writer
Draft or update user-focused GitHub Release Notes from verified tags, commits, pull requests, existing releases, and supplied changelog baselines. Use when preparing prerelease or stable release notes, turning GitHub's generated What's Changed list into a curated narrative, documenting upgrades or breaking changes, or…
c-12-closeout
Close out approved Agents Remember edits by preserving approval authority, mandatory strict code quality before code commit, missing-onboarding checks, external-memory refresh, memory quality, ledger alignment, and no automatic push.