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 artem-from-ua/claude-plugins --skill semver-guidegit clone --depth 1 https://github.com/artem-from-ua/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/skills/artem-from-ua/claude-plugins/semver-guide)<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/semver-guide"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/semver-guide/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/artem-from-ua/claude-plugins/semver-guide"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/semver-guide.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.00081 | $0.00805 |
| Opus 5 | $0.00041 | $0.00402 |
| Sonnet 5 | $0.00016 | $0.00161 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
semver-guide 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 9d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SemVer 2.0.0 Quick Reference
Version Format
MAJOR.MINOR.PATCH — e.g., 2.1.0
When to reset: incrementing MINOR resets PATCH to 0; incrementing MAJOR resets both.
When to Increment
PATCH (x.y.Z)
Backwards-compatible bug fixes. No new API surface.
- Fixed crash on empty input
- Corrected typo in error message
- Performance optimization (same behavior)
- Fixed race condition
MINOR (x.Y.0)
New features, backwards-compatible. Reset PATCH to 0.
- Added new API endpoint / function / command
- Added optional parameter with default value
- New configuration option (with sensible default)
- Deprecated old API (still works)
MAJOR (X.0.0)
Breaking changes. Reset MINOR and PATCH to 0.
- Removed public API / function / command
- Changed function signature (added required params)
- Renamed public interface
- Changed default behavior incompatibly
- Dropped platform or dependency support
Decision Tree
Changed files → excluded (docs, LICENSE, .gitignore)? → YES → No bump needed
→ NO ↓
Did you remove / rename / break existing API? → YES → MAJOR
Did you add new public API or feature? → YES → MINOR (at minimum)
Did you fix a bug? → YES → PATCH
Refactoring, internal restructure only? → PATCH (or skip if truly zero user impact)
Initial Development (0.x.y)
0.x.y signals the API is not yet stable — anything may change.
- Start at
0.1.0 - Use
0.x.yfreely during development - Declare
1.0.0for the first stable public release
Pre-release Versions
Format: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-beta.2, 1.0.0-rc.1
Precedence: alpha < alpha.1 < beta < rc.1 < release
Use for unstable or pre-release testing builds.
Conflict Resolution (Rebase / Merge)
When you rebase and find a version conflict:
- Check base branch version:
git show <baseBranch>:<versionFile> | jq -r '.version' - Compare with your bumped version:
- Base is higher → increment from base (not your original)
- Base is same → increment again (concurrent PR)
- Base is lower → keep yours (already correct)
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.
- 9d ago First seen · 95 lines · 81 tokens per session scan A c2bc7d652b1b
semver-guide is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 805 once invoked, about $0.0004 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-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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.