Borrowing it
Nothing to install: this file belongs to greenpau/go-authcrunch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/greenpau/go-authcrunch/main/.codex/skills/release-and-versioning/SKILL.mdgit clone --depth 1 https://github.com/greenpau/go-authcrunchWrote 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/greenpau/go-authcrunch/release-and-versioning)<a href="https://agentmods.dev/skills/greenpau/go-authcrunch/release-and-versioning"><img src="https://agentmods.dev/badge/skills/greenpau/go-authcrunch/release-and-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/greenpau/go-authcrunch/release-and-versioning"><img src="https://agentmods.dev/badge/skills/greenpau/go-authcrunch/release-and-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.00044 | $0.00933 |
| Opus 5 | $0.00022 | $0.00466 |
| Sonnet 5 | $0.00009 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
release-and-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 yesterday.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release and Versioning
Authority and Projections
VERSION is exactly 1.<minor>.<patch>, optionally terminated by one newline,
with no leading zeros or prerelease/build suffixes. The major stays 1.
Expose patch and minor operations only; do not add a major bump. Adding a
feature does not itself authorize bumping or publishing a release.
assets/scripts/version.py validates that namespace and the fallback metadata
in cmd/authdbctl/main.go and pkg/identity/database.go. make version-check
is read-only. make version-sync invokes the pinned go tool versioned -release -sync for both projections, then checks them. Committed branch/commit
fallbacks are empty; actual build metadata comes from linker flags. Ordinary
builds/tests never synchronize source or run go mod tidy implicitly.
The go.mod tool block and its requirements pin tested, versioned, and
golint; use go tool so a globally installed binary cannot silently change
repository behavior. Tool upgrades are explicit dependency changes.
Artifact Identity and CI
make artifact-id validates projections and produces
v<VERSION>_<UTC YYYYMMDDTHHMMSSZ>_<12-character SHA> for branch, pull-request,
and manual builds. An exact v<VERSION> tag produces v<VERSION>; any other
tag fails. GITHUB_SHA binds the identity to the actual checked commit, and
GITHUB_OUTPUT receives validated version and artifact_id values.
.github/workflows/test.yml is reusable by the release workflow. It runs
make ci-check and uploads the complete ignored .coverage/ bundle, including
failure evidence, as go-authcrunch_coverage_<artifact-id>. Coverage is a
workflow diagnostic artifact, separate from published distributions.
.github/workflows/release.yml requires the reusable test job before publishing,
checks the exact annotated tag and synchronized version, then runs pinned
GoReleaser with write permission confined to that job. .goreleaser.yaml owns
Linux/Windows/Darwin amd64/arm64 authdbctl builds, checksums, and linker
metadata. Preserve immutable action pins and avoid publishing every local tag.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 77 lines · 44 tokens per session scan A 94b72366b655
release-and-versioning is a skill published in the GitHub repository greenpau/go-authcrunch (59 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 933 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-13.
Other skills, from other repositories
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".