semantic-versioning

semantic-versioning is a skill for Claude Code from tuliosousapro/SaaS-blueprint. It costs 63 tokens per session (472 once invoked), scanned A, original, MIT.

A release-versioning guide that applies Semantic Versioning, a system where version numbers show the kind of change made. It checks project files and changes to choose and apply the next version.

In plain words
What is it for?
Use it to bump a version, prepare a release, or update the version after reviewing commits and changelog entries.
Why use it?
It removes guesswork when releasing software and helps keep the version in the changelog and project metadata consistent.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the SaaS-blueprint plugin — 14 skills shipped together

Good fit Use it to bump a version, prepare a release, or update the version after reviewing commits and changelog entries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tuliosousapro/saas-blueprint/semantic-versioning
Install

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.

Any agent
npx skills add tuliosousapro/SaaS-blueprint --skill semantic-versioning
Clone the repo
git clone --depth 1 https://github.com/tuliosousapro/SaaS-blueprint

Made for: Claude Code.

Or install SaaS-blueprint, the plugin that ships this one along with the rest of its 14 skills.

Wrote 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.

agentmods badge for semantic-versioning

README.md
[![agentmods](https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/semantic-versioning/github.svg)](https://agentmods.dev/skills/tuliosousapro/saas-blueprint/semantic-versioning)
Your own site
<a href="https://agentmods.dev/skills/tuliosousapro/saas-blueprint/semantic-versioning"><img src="https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/semantic-versioning/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.

agentmods 80×15 button for semantic-versioning

Your own site · 80×15
<a href="https://agentmods.dev/skills/tuliosousapro/saas-blueprint/semantic-versioning"><img src="https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/semantic-versioning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 472 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.00472
Opus 5 $0.00032 $0.00236
Sonnet 5 $0.00013 $0.00094
Haiku 4.5 $0.00006 $0.00047

Measured 10d ago against content hash 45da7f3f3528, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

semantic-versioning 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 10d 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.

skills/semantic-versioning/SKILL.md · 45 lines

What it actually says

Semantic Versioning Skill

Instructions

1. Detect Current Version

  • Read the latest version from CHANGELOG.md (e.g., the most recent header ## [X.Y.Z]).
  • Read the version from .github/repository-metadata.json.
  • If they differ, flag the mismatch to the user and ask which is authoritative.

2. Analyze Changes

Scan the changes since the last release:

  • If using changelog skill: Look at the items under [Unreleased] or the new version block being prepared.
  • If using git log: Scan for Conventional Commits types.

3. Determine Increment Type

Follow these priority rules:

  1. MAJOR (X.0.0): Any "BREAKING CHANGE" footer or ! after the type (e.g., feat!:).
  2. MINOR (x.Y.0): Any feat commit or "Added" entry in the changelog.
  3. PATCH (x.y.Z): Any fix, perf, refactor commit or "Fixed"/"Changed" entry in the changelog.
  4. No Change: If only docs, chore, style, test, build, or ci changes are found, default to PATCH unless the user specifies otherwise.

4. Apply Version Update

Update the following files in a single pass:

  • CHANGELOG.md: Rename the ## [Unreleased] section to ## [NEW_VERSION] - CURRENT_DATE or update the latest entry.
  • .github/repository-metadata.json: Update the "version" field.

Quality Gates

  • Version follows MAJOR.MINOR.PATCH format.
  • No regression in version number.
  • All version-tracking files are synchronized.
  • Date in CHANGELOG.md is in YYYY-MM-DD format.
Changes

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.

  1. 10d ago First seen · 45 lines · 63 tokens per session scan A 45da7f3f3528

Subscribe to this mod's changes

semantic-versioning is a skill published in the GitHub repository tuliosousapro/SaaS-blueprint (4 stars, last pushed 9d ago), licensed MIT. It adds 63 tokens to every session and 472 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.