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 GktuOktay/ai-skills --skill version-bumpgit clone --depth 1 https://github.com/GktuOktay/ai-skillsWrote 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/gktuoktay/ai-skills/version-bump)<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/version-bump"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/version-bump/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/gktuoktay/ai-skills/version-bump"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/version-bump.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.00049 | $0.01023 |
| Opus 5 | $0.00024 | $0.00511 |
| Sonnet 5 | $0.00010 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
Version Bumping and Release Management 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Versioning and Release Management
Proper versioning and release management ensure predictable deployments, clear communication with users, and safe rollback mechanisms.
1. Semantic Versioning (SemVer) Rules
Semantic Versioning follows the format: MAJOR.MINOR.PATCH (e.g., 2.14.3).
- MAJOR (Incompatible Changes): Increment when you make incompatible API changes. Existing clients will break if they upgrade without code changes. (e.g., removing a deprecated endpoint, changing a function signature).
- MINOR (New Features): Increment when you add functionality in a backward-compatible manner. Existing clients can upgrade safely. (e.g., adding a new API endpoint, adding a non-breaking optional parameter).
- PATCH (Bug Fixes): Increment when you make backward-compatible bug fixes. No new features are added. (e.g., fixing a memory leak, resolving a crash).
Note: Version 0.y.z is for initial development. Anything MAY change at any time. The public API should not be considered stable.
2. Pre-release Versions
Used for testing and stabilization before a major/minor release. Appended to the version number with a hyphen.
- Alpha (
v2.0.0-alpha.1): Internal testing, highly unstable, features may be incomplete. - Beta (
v2.0.0-beta.2): Feature complete, public testing, bugs are expected. - RC (Release Candidate) (
v2.0.0-rc.1): Potential final release, testing for critical regressions only.
3. Conventional Commits and Changelog Generation
Manual changelogs are error-prone and tedious. Use Conventional Commits to automate them.
Format: <type>[optional scope]: <description>
Common Types:
feat:(New feature) -> Triggers a MINOR bump.fix:(Bug fix) -> Triggers a PATCH bump.docs:,style:,refactor:,test:,chore:-> Usually do not trigger a release or changelog entry.BREAKING CHANGE:(In the footer) -> Triggers a MAJOR bump, regardless of the type.
By strictly formatting commit messages, tools can automatically calculate the next version number and generate a CHANGELOG.md.
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 · 68 lines · 49 tokens per session scan A 3f92afb1da5d
Version Bumping and Release Management is a skill published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 1,023 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, canonical sync, Core preview checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
changelog
AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.
utility-pm-release-conductor
Walk the guided 6-gate release runbook (G0 readiness, G1 adversarial review, G2 version bump and CHANGELOG, G2.5 commit and re-verify, G3 tag and push, G4 post-tag hygiene) via the pm-release-conductor sub-agent. Refuses gate bypasses and tags only the re-verified SHA. Use when cutting a pm-skills release.
utility-pm-changelog-curator
Draft CHANGELOG entries from git log via the pm-changelog-curator sub-agent, applying the repo hygiene rules (describe what changed, public paths only, no attribution trailers). Returns a layered draft with a status summary for maintainer review; refuses a dirty working tree unless --committed-only is passed. Use when…
deliver-release-notes
Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.