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/genai-io/san/releasenpx skills add genai-io/san --skill releasegit clone --depth 1 https://github.com/genai-io/sanWrote 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/genai-io/san/release)<a href="https://agentmods.dev/skills/genai-io/san/release"><img src="https://agentmods.dev/badge/skills/genai-io/san/release.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.00075 | $0.02044 |
| Opus 5 | $0.00037 | $0.01022 |
| Sonnet 5 | $0.00015 | $0.00409 |
| Haiku 4.5 | $0.00007 | $0.00204 |
Grade A, and why
release 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.
How it starts
The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release — Version Bump, Tag, and Changelog
Create a new release with a structured changelog and author attribution.
Arguments
<version>— The version to release (e.g.1.19.1,v2.0.0). Thevprefix is optional in input but always used for the git tag.
If no version is given, detect the current version and suggest the next one (see Step 1).
Constraints
- Only patch (
x.y.Z) or minor (x.Y.0) bumps. Never bump major — the module path has no/vNsuffix, so a major bump would violate Go v2+ rules. - All version tags use the
vprefix (e.g.v1.20.0).
Workflow
0. Ensure on main and pull from upstream
Verify you are on the main branch. If not, stash any pending work and switch:
git branch --show-current
If not on main: git stash && git checkout main
Then pull the latest upstream codebase:
git pull upstream main --rebase
If there are merge conflicts, resolve them before proceeding.
1. Detect current version and suggest the next
Read the current version and identify changes since the last tag:
-
Read the code version from
cmd/san/main.go:grep 'var version = ' cmd/san/main.go -
Get the latest git tag:
git describe --tags --abbrev=0Strip the
vprefix for comparison. -
Compare. If the code version and tag version differ, warn the user — the code may be out of sync with releases.
-
Get commits since the latest tag:
git log --oneline <prev_tag>..HEAD -
Suggest the next semver bump based on commit content:
- Major (
X.0.0): commits withBREAKING CHANGE, or that remove/rename public APIs - Minor (
x.Y.0):feat:commits, new functionality, new features - Patch (
x.y.Z):fix:commits, bug fixes, docs, chores, refactors
Default to patch if the commits don't clearly indicate otherwise.
- Major (
-
Ask the user. Use AskUserQuestion, showing the current code version and the suggested next version:
- Option 1: the suggested version (e.g.
v1.19.1— patch) - Option 2: one step larger bump (e.g.
v1.20.0— minor) - The "Other" option lets the user enter a custom version.
- Option 1: the suggested version (e.g.
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 · 238 lines · 75 tokens per session scan A ad7e425455ee
release is a skill published in the GitHub repository genai-io/san (76 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 2,044 once invoked, about $0.0004 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-publish
Release, publish, CalVer tag push, npm publish, 배포, 릴리즈 for senpi. Use for the canonical release flow, GitHub tag/release publication, and npm publishing.
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.
pi-release-workflow
Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.
pi-review-gated-delivery
Use when coordinating review-gated delivery of discrete GitHub issues between one implementation peer and a review-only lead, with user-owned Changesets and approval-gated commits.
github
Interact with GitHub using the gh CLI. Use for issues, PRs, CI runs, releases, and advanced API queries.