Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/thettwe/nyannnpx agentmods add skills/thettwe/nyann/releaseWrote 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/thettwe/nyann/release)<a href="https://agentmods.dev/skills/thettwe/nyann/release"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/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.1 | $0.00207 | $0.02819 |
| Opus 5 | $0.00103 | $0.01409 |
| Sonnet 5 | $0.00041 | $0.00564 |
| Haiku 4.5 | $0.00021 | $0.00282 |
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 3d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release
Wraps bin/release.sh. Default strategy is conventional-changelog:
walk the commit range since the last matching tag, group commits by
Conventional Commits type, prepend a CHANGELOG block, commit the
changelog, then annotated-tag v<version>.
0. Drift check (quick, non-blocking)
Run bash bin/session-check.sh --flow=release. If it produces output,
surface the line to the user verbatim. Do not block the flow.
1. Suggest version (when not explicitly provided)
When the user does not supply an explicit --version, run
bin/recommend-version.sh to suggest one:
bin/recommend-version.sh --target <cwd> [--tag-prefix <p>]
Show the recommendation to the user:
Based on commits since
<current>, I'd suggest<recommended>(<bump>bump —<reason>). Shall I proceed with<recommended>, or would you prefer a different version?
Wait for confirmation before proceeding. The user can accept, override with a different version, or abort.
When the user does supply an explicit version (e.g. "release v2.0.0"), skip this step entirely — don't second-guess them.
When the user says "bump minor" / "bump major" / "bump patch", run
recommend-version.sh to get the current version, then apply the
requested bump type (ignore the script's own recommendation). Confirm
the computed version with the user before proceeding.
2. Collect inputs
--version <x.y.z>— required forrelease.sh. Must be semver (orx.y.z-prerelease). Populated from step 1 when the user accepted the suggestion, or from their explicit input.--strategy— defaults toconventional-changelog. Override tomanualwhen the user says "just tag it, skip the changelog".changesets/release-pleaseare soft-skip values: the script emits a skip record pointing the user at those tools directly.--changelog <path>— defaults toCHANGELOG.md. Override when the repo uses a different file.--tag-prefix <p>— defaults tov. Override for monorepos that namespace tags (api-v1.2.0).--from <ref>— defaults to the latest tag matchingtag_prefix. Override when the user says "include everything since commit X".
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.
- 3d ago First seen · 241 lines · 207 tokens per session scan A 768fe5238300
release is a skill published in the GitHub repository thettwe/nyann (6 stars, last pushed 8d ago), licensed MIT. It adds 207 tokens to every session and 2,819 once invoked, about $0.0010 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-03.
Other skills, from other repositories
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
create-release-checklist
Create a release checklist and GitHub issue for an R package. Use when the user asks to "create a release checklist" or "start a release" for an R package.
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
craft-plugin-release
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist…
publish-github-release
Use this whenever the user asks to ship, publish, release, tag, or cut a new version of the project — OR when CHANGELOG.md has an "Unreleased" / in-progress section ready to be shipped. The skill bumps the version across all version-bearing files, regenerates the CHANGELOG entry from git log since the last tag…
wp-org-submission
Use when submitting a WordPress plugin to the WP.org directory for the first time, deploying a new version via SVN (plugins.svn.wordpress.org trunk, tags, assets), fixing a reviewer rejection (17-issue catalog with exact reviewer quotes), writing or correcting readme.txt (Stable tag, Changelog, Upgrade Notice…