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 sonichi/sutando --skill releasegit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/release)<a href="https://agentmods.dev/skills/sonichi/sutando/release"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/release/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/sonichi/sutando/release"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/release.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.00068 | $0.01020 |
| Opus 5.5 | $0.00027 | $0.00408 |
| Sonnet 5.5 | $0.00014 | $0.00204 |
| Haiku 4.5 | $0.00007 | $0.00102 |
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 1mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Use docs/release-process.md as policy. Do not
duplicate or reinterpret it here. This skill turns that policy into an
evidence-backed workflow.
Choose a mode
- Prepare: inspect changes, update documentation and release artifacts, run gates, and write a proposal. This is the default.
- Publish: create the tag and GitHub Release only after explicit owner confirmation in the current conversation.
Never infer publish permission from “prepare,” “get ready,” a green CI run, or an approved release PR.
Prepare
-
Read
docs/release-process.mdcompletely. -
Resolve the repository and workspace:
REPO="$(git rev-parse --show-toplevel)" WORKSPACE="$(bash "$REPO/scripts/sutando-config.sh" workspace)" -
Identify the last release tag and the exact candidate SHA. Compare the tag to the candidate; do not rely only on PR titles.
-
Classify the change set:
- user-visible features and fixes;
- configuration, schema, API, protocol, or permission changes;
- migrations and rollback implications;
- new or changed skills;
- install, setup, operations, and troubleshooting changes.
-
Run the documentation audit:
python3 skills/release/scripts/docs_audit.py -
Perform a docs-impact pass. For every user-visible or contract change, identify the canonical document in
docs/catalog.json. Update that document, itslast_verifieddate, README navigation when appropriate, migration or upgrade guidance, andCHANGELOG.md. Do not copy canonical text into a second document. -
Prepare one release PR containing only release artifacts and documentation. Do not mix product fixes into it; list unresolved fixes as blockers. It records the entry after the tag (see Publish step 2) and is not a precondition for publishing.
-
Run every applicable hard gate from
docs/release-process.md, including the fresh-clone health check, headline-feature smoke, migration idempotency, and prior-release-to-candidate upgrade smoke. Record exact commands, candidate SHA, exit status, and observable evidence. Never invent or summarize an unexecuted gate as passing. -
Write the proposal to
$WORKSPACE/notes/release-proposals/proposed-vX.Y.Z.mdwith:- candidate version and SHA;
- SemVer rationale;
- user-facing summary and CHANGELOG draft;
- documentation-impact table;
- gate evidence;
- migrations, rollback, and known gaps;
- unresolved blockers;
- explicit owner decision line:
publish: pending owner confirmation.
-
Report the proposal and release PR. Stop before tagging or publishing.
What ships with it
2 files 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.
- 1mo ago First seen · 101 lines · 68 tokens per session scan A 32e0bd1fbbae
release is a skill published in the GitHub repository sonichi/sutando (397 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 1,020 once invoked, about $0.0003 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
GitHub integration — repos, issues, pull requests, branches, CI/Actions, code search, releases, gists, collaborators, labels, milestones, reviews, notifications, stars, forks, and more via the GitHub API.
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
release
Cut and maintain Observal release branches, prepare alpha, beta, RC, stable, and patch releases, backport merged main PRs, inspect release status, verify published artifacts, and recover failed release operations. Use for Observal maintainer release tasks and release-process changes, not for installing or upgrading an…
release
Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever…
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.