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 skills add LenoSeibert/semver-plugin --skill semver-reviewgit 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/semver-review)<a href="https://agentmods.dev/skills/lenoseibert/semver-plugin/semver-review"><img src="https://agentmods.dev/badge/skills/lenoseibert/semver-plugin/semver-review.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.00055 | $0.00316 |
| Opus 5 | $0.00028 | $0.00158 |
| Sonnet 5 | $0.00011 | $0.00063 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
semver-review 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 6d 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
SemVer Release Review
Inspect the public API definition and the actual changes. Include documented interfaces such as libraries, CLIs, protocols, file formats, configuration, schemas, and observable behavior when consumers can depend on them.
Review
- Identify the current released version and public API boundary.
- List consumer-visible changes, separating incompatible changes, backward-compatible features/deprecations, fixes, and internal-only work.
- Select the highest required bump using SemVer 2.0.0.
- Verify that lower components reset, the proposed version has not already been released, and pre-release/build labels are valid when used.
- Flag uncertainty when compatibility cannot be established from evidence.
Do not downgrade a bump because a break seems small, optional, or easy to
migrate. Do not upgrade a bump merely because the implementation diff is
large. Under 0.y.z, report that SemVer permits arbitrary change and evaluate
the repository's documented pre-1.0 policy separately.
Output
Lead with Recommendation: <version or bump>. Then give only evidence-backed
findings, highest severity first, with file locations when reviewing a repo.
End with missing evidence or No SemVer blockers found.
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.
- 6d ago First seen · 32 lines · 55 tokens per session scan A 5eea3341dea7
semver-review is a skill published in the GitHub repository LenoSeibert/semver-plugin (1 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 316 once invoked, about $0.0003 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
agentplane-release-and-packaging-operator
Use when preparing, validating, publishing, auditing, or recovering an Agentplane release, especially package build ordering, version parity, npm/GitHub/GHCR/external distribution publication, public install smoke tests, hosted publish evidence, or release CI failures.
checking-release-readiness
Records a ship, block, defer, or ship-with-risk decision that ties baseline, evidence status, residual risk, rollback, monitoring, and handoff together. Use when a packet, PR, release, dependency change, or agent-authority change approaches merge. Do not use early in development before evidence exists.
brpr
(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.
release
Automate the release process. Use when user says "cut a release", "new version", "bump version", "publish release", or anything about versioning and publishing.
release-deploy
Prepare a public open-source project for release and deploy it to a detected target. Use at a release or submission boundary to verify setup, docs, secrets, tests, lint, build, and licenses, then follow the target-specific deployment path. Runs expensive checks sequentially. Never publishes, tags, commits, pushes, or…
ship-it
Branch (if needed), commit, and push the current changes to remote in one step. Invoke only when the user explicitly runs /ship-it or asks to branch-commit-push — it reminds you to review first, then commits and pushes. Args: [branch-name-or-issue-id].