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 tuliosousapro/SaaS-blueprint --skill semantic-versioninggit clone --depth 1 https://github.com/tuliosousapro/SaaS-blueprintWrote 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/tuliosousapro/saas-blueprint/semantic-versioning)<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.
<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>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.00063 | $0.00472 |
| Opus 5 | $0.00032 | $0.00236 |
| Sonnet 5 | $0.00013 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
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.
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
changelogskill: 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:
- MAJOR (X.0.0): Any "BREAKING CHANGE" footer or
!after the type (e.g.,feat!:). - MINOR (x.Y.0): Any
featcommit or "Added" entry in the changelog. - PATCH (x.y.Z): Any
fix,perf,refactorcommit or "Fixed"/"Changed" entry in the changelog. - No Change: If only
docs,chore,style,test,build, orcichanges 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_DATEor update the latest entry. - .github/repository-metadata.json: Update the
"version"field.
Quality Gates
- Version follows
MAJOR.MINOR.PATCHformat. - No regression in version number.
- All version-tracking files are synchronized.
- Date in
CHANGELOG.mdis inYYYY-MM-DDformat.
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.
- 10d ago First seen · 45 lines · 63 tokens per session scan A 45da7f3f3528
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.
Other skills, from other repositories
ios-appstore-builder
Prepare, configure, and publish iOS apps to the Apple App Store. Covers certificates, provisioning profiles, TestFlight, App Store submission, and review guidelines.
app-release-manager
Manage the complete mobile app release lifecycle from versioning to store submission.
changelog-automator
Professional Changelog Automator Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.
changelog-generator
Professional Changelog Generator Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.
release-manager
Professional Release Manager Expert skill. Build robust, automated deployment pipelines and configure cloud infrastructure as code.
semantic-versioning
Professional Semantic Versioning Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.