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/rexleimo/aios/versioning-by-impactnpx skills add rexleimo/aios --skill versioning-by-impactgit clone --depth 1 https://github.com/rexleimo/aiosWrote 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/rexleimo/aios/versioning-by-impact)<a href="https://agentmods.dev/skills/rexleimo/aios/versioning-by-impact"><img src="https://agentmods.dev/badge/skills/rexleimo/aios/versioning-by-impact.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 | $0.00029 | $0.00379 |
| Opus 5 | $0.00015 | $0.00189 |
| Sonnet 5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
versioning-by-impact 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 5d 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
Versioning by Impact
Overview
Apply Semantic Versioning decisions from actual change impact, not from task size.
Impact Rules
none: no repository file changes.patch: backward-compatible fixes, docs updates, translation/content updates, non-breaking refactors.minor: backward-compatible new features or new capabilities.major: any breaking change to CLI behavior, config contract, file layout contract, or documented usage.
Required Output Format
Always report these 4 fields in final handoff:
Version Impact: none|patch|minor|majorRecommended Version: vX.Y.Z -> vA.B.C(orno change)Why: <one-sentence reason>Release Notes:short bullet list
Repository Commands
- Read current version:
cat VERSION - Bump version + changelog entry:
scripts/release-version.sh <patch|minor|major> "summary" - Preview only:
scripts/release-version.sh --dry-run <patch|minor|major> "summary"
Default Behavior
If impact is none, do not bump version.
If impact is patch|minor|major, update both VERSION and CHANGELOG.md before commit.
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.
- 5d ago First seen · 46 lines · 29 tokens per session scan A c06f78e0a451
versioning-by-impact is a skill published in the GitHub repository rexleimo/aios (52 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 379 once invoked, about $0.0001 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 Engineering
Semantic versioning, changelog generation, and release/hotfix management so releases are predictable and reversible.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
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
Release pipeline for CLI, mobile, web, and server. Guides through version bumping, building, testing, publishing, and deploying. Replaces the old interactive release-it flow with a Claude Code-native experience. Use when user types /release or asks to release, publish, deploy, or ship any component.
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.