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.
git clone --depth 1 https://github.com/thettwe/nyannWrote 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/commands/thettwe/nyann/release)<a href="https://agentmods.dev/commands/thettwe/nyann/release"><img src="https://agentmods.dev/badge/commands/thettwe/nyann/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/commands/thettwe/nyann/release"><img src="https://agentmods.dev/badge/commands/thettwe/nyann/release.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.00037 | $0.00755 |
| Opus 5.5 | $0.00015 | $0.00302 |
| Sonnet 5.5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
nyann: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.
What it actually says
Plugin root: This is a Claude Code plugin, NOT a CLI tool. Do NOT
search via which, npm list, pip list, or brew list. This file
is at <plugin_root>/commands/. All scripts: <plugin_root>/bin/.
Read the matching skills/*/SKILL.md for the full flow.
/nyann:release
Wraps bin/release.sh. Flow for conventional-changelog:
- Find latest tag matching
tag_prefix(defaultv). Walk commits since. - Group commits by Conventional Commits type. Breaking-changes (subject
!) render first. - Prepend the block to CHANGELOG.md (creating the file with a header if missing).
- Release commit:
chore(release): v<version>. - Annotated tag
v<version>. - Optional
--pushsends tag + commit toorigin.
Profiles may declare an optional release block (strategy, changelog_path, tag_prefix) — the skill honors it when present.
--wait-for-checks is the safety net for "don't tag a broken build": it resolves the PR by exact HEAD SHA (headRefOid) and blocks on bin/wait-for-pr-checks.sh until CI passes. Output gains ci_gate: { outcome, pr_number? } on success so consumers can prove the gate ran. Because a pushed tag is marketplace-consumed, --push auto-enables this gate when origin is a GitHub remote and gh is authenticated — degrading gracefully (warn, not fail) when there's no PR or no authenticated gh; pass --no-wait-for-checks to opt out. Passing --wait-for-checks explicitly makes it strict: no PR matching HEAD is then a hard error — pass --allow-no-pr for first-cut or local-only releases.
See skills/release/SKILL.md for full flow, dry-run guidance, and breaking-change handling.
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 · 49 lines · 37 tokens per session scan A 7b60d6ccfdbf
nyann:release is a command published in the GitHub repository thettwe/nyann (7 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 755 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-31.
Other commands, from other repositories
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
ship
Open a pull request for the current branch, drive it green, and merge it.
release
Cut a Major.Minor release from the Increment.
changelog
Export user-facing release notes from the version history (derived, never edits the ledger).
create-new-release
Cut a new release — bump version, write CHANGELOG entry, commit and tag.
sdlc-release
Release planning and rollout - versioning, staging, gradual deployment, rollback.