agentmods.dev

nyann:release

A release command that turns Conventional Commits—commits with standard labels such as feature or fix—into a changelog entry, release commit, and annotated Git tag. A Git tag is a named marker for a specific version of the code.

In plain words
What is it for?
Use it to prepare versioned releases, update CHANGELOG.md, create tags, and optionally push the release to the remote repository.
Why use it?
It removes repetitive release bookkeeping and can wait for continuous-integration checks before tagging a version.

Command

6 3d ago A scan 37 tokens original MIT
View the source file thettwe/nyann
Install

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.

agentmods
npx agentmods add commands/thettwe/nyann/release
Clone the repo
git clone --depth 1 https://github.com/thettwe/nyann
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 755 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00755
Opus 5 $0.00018 $0.00378
Sonnet 5 $0.00007 $0.00151
Haiku 4.5 $0.00004 $0.00076

Measured 2d ago against content hash 7b60d6ccfdbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

commands/release.md · 49 lines

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:

  1. Find latest tag matching tag_prefix (default v). Walk commits since.
  2. Group commits by Conventional Commits type. Breaking-changes (subject !) render first.
  3. Prepend the block to CHANGELOG.md (creating the file with a header if missing).
  4. Release commit: chore(release): v<version>.
  5. Annotated tag v<version>.
  6. Optional --push sends tag + commit to origin.

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.

Changes

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.

  1. 2d ago First seen · 49 lines · 37 tokens per session scan A 7b60d6ccfdbf

Subscribe to this mod's changes

nyann:release is a command published in the GitHub repository thettwe/nyann (6 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 755 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-08-31.

Git and workflowReleasesclaude-codeclaude-code-pluginclaude-skillsgithubgovernancescaffolding
Related

Other commands, from other repositories

create-namespace

Slash command that creates a new namespace file under system/namespaces/ in the personal repo, with lifecyclestate: scratch.

starmynd-org/infinite-brain-os · 0 tokens

generate-release-notes

Generate comprehensive release notes from merged PRs between releases.

toolprint/hypertool-mcp · 10 tokens

review-renovate

Review and merge renovate PRs with automerge configuration updates.

liam-hq/liam · 11 tokens

release

Perform a full release: generate release notes, bump version, commit, tag, and push.

elirantutia/vibeyard · 0 tokens

SHIP_RELEASE

Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.

Osiris-DevWorks/smart-citizen · 34 tokens

release

The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.

azrtydxb/procoder · 30 tokens