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/artem-from-ua/claude-plugins/semver-setupnpx skills add artem-from-ua/claude-plugins --skill semver-setupgit 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-setup)<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/semver-setup"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/semver-setup.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.00068 | $0.00945 |
| Opus 5 | $0.00034 | $0.00473 |
| Sonnet 5 | $0.00014 | $0.00189 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
semver-setup 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semver Setup
Configure semantic versioning enforcement for this project.
Steps
1. Detect existing config and version files
Check for existing configuration:
- Read
.claude-plugin/semver.jsonif present (use as defaults for all questions) - Auto-detect common version files in the project root:
package.json,pyproject.toml,Cargo.toml,.claude-plugin/plugin.json,version.txt - For monorepos: also scan one level deep (e.g.,
packages/*/package.json)
Show the user what was found.
2. Ask: which version files to track
Use AskUserQuestion with multiSelect: true. List detected files with descriptions:
package.json— npm/Node.js projectspyproject.toml— Python projects (field:project.versionortool.poetry.version)Cargo.toml— Rust projects (field:package.version).claude-plugin/plugin.json— Claude Code plugins (field:version)- Other: ask user to enter path manually
For each selected file, ask:
- Field path (dot notation for nested) — default by file type:
versionfor JSON,project.versionfor pyproject.toml,package.versionfor Cargo.toml - Format —
json/toml/yaml/text(auto-detected from extension if possible)
3. Ask: trigger strategy
Use AskUserQuestion (single select):
auto— Claude evaluates each change and decides. New feature → MINOR, bug fix → PATCH, breaking change → MAJOR, docs/config only → skip. (Recommended)always— Every commit with source file changes must include a version bump. No exceptions. Good for strict release workflows.
4. Ask: enforcement level
Use AskUserQuestion (single select):
ask— Warn and ask for confirmation before proceeding without a bump. (Default)deny— Block commit/push/PR until a version bump is staged.allow— No enforcement. Only session rules, no hook blocking.
5. Ask: base branch
Use AskUserQuestion (single select):
main(Default)masterdevelop- Other (user enters custom name)
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 · 107 lines · 68 tokens per session scan A b7766fecfc09
semver-setup is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed 20d ago), licensed MIT. It adds 68 tokens to every session and 945 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-30.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…