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 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/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/rexleimo/aios/versioning-by-impact"><img src="https://agentmods.dev/badge/skills/rexleimo/aios/versioning-by-impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00803 |
| Opus 5.5 | $0.00012 | $0.00321 |
| Sonnet 5.5 | $0.00006 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00080 |
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 23d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Release Ordering (submodule first)
A host release archives the rex-harness submodule work tree, so the version it
announces only exists if that submodule commit is itself a published
(tarball-bearing) rex-harness release.
- Release rex-harness first: tag
vX.Y.Z, push, let its release workflow produce the GitHub Release asset. Then cut the host release whose gitlink points at that tagged commit. - Never cut a host release over an untagged submodule commit. The host changelog would cite a rex-harness version that exists nowhere on the rex-harness remote, standalone rex-harness consumers get nothing, and the bundled kernel cannot be traced back to a release point.
- If an already-published host release turns out to cite an untagged submodule version, retroactively tag and release that submodule commit: the gap is a traceability defect in shipped artifacts, not a cosmetic one.
The gate is enforced by scripts/release-preflight.sh (and the .ps1 twin) via
scripts/check-release-submodule.mjs; it fails closed when the tag state cannot
be proven.
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
When a release is requested, also state whether the submodule commit is already a published rex-harness release, and in which order the two tags must go out.
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" - Refresh the machine-readable LLM index after any version/changelog/post change:
node scripts/generate-llms-txt.mjs(verify only: add--check).docs-site/llms.txtis generated fromsite-sources/llms.src.mdplusVERSION,CHANGELOG.mdandblog-site/*.md; a hand-edited copy drifts (the live file once advertised v5.20.0 while v6.2.0 was shipping, and listed 24 of 68 published posts).
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.
- 23d ago Changed · +29 lines 5f06b72ee0a4
- 1mo ago Changed 568901facc47
- 1mo ago Changed dd5254c0e04e
- 1mo ago Changed 5bc18d983375
- 1mo 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 (56 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 803 once invoked, about $0.0001 per session on Opus 5.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
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.
automating-devops
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image…
release-init
Detect project type and generate a tailored project-level /release skill. Run once per project to set up releasing.
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.
changelog
Generate or update a CHANGELOG.md in Keep a Changelog format from real git history. Use when cutting a release, tagging a version, or asked "what changed since…".
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.