release

release is a command for Claude Code from hummer98/nanobanana-adc. It costs 31 tokens per session (1,488 once invoked), scanned A, original, MIT.

A command that carries out a release workflow for the nanobanana-adc project, including version checks, changelog updates, tests, builds, and release preparation.

In plain words
What is it for?
Use it to prepare releases automatically, either by choosing a version yourself or deriving one from recent commits.
Why use it?
It gathers the recurring checks and file updates needed before publishing a new project version.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is npm run typecheck && npm test && npm run build && ./bin/nanobanana-adc --version.

Part of the nanobanana-adc plugin — 1 skill, 1 command shipped together

Good fit Use it to prepare releases automatically, either by choosing a version yourself or deriving one from recent commits.

Compare 6 commands from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/hummer98/nanobanana-adc
agentmods
npx agentmods add commands/hummer98/nanobanana-adc/release

Made for: Claude Code.

Or install nanobanana-adc, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/commands/hummer98/nanobanana-adc/release/github.svg)](https://agentmods.dev/commands/hummer98/nanobanana-adc/release)
Your own site
<a href="https://agentmods.dev/commands/hummer98/nanobanana-adc/release"><img src="https://agentmods.dev/badge/commands/hummer98/nanobanana-adc/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/commands/hummer98/nanobanana-adc/release"><img src="https://agentmods.dev/badge/commands/hummer98/nanobanana-adc/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,488 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00031 $0.01488
Opus 5 $0.00015 $0.00744
Sonnet 5 $0.00006 $0.00298
Haiku 4.5 $0.00003 $0.00149

Measured 10d ago against content hash a7a179dd96f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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

.claude/commands/release.md · 134 lines

How it starts

The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/release

nanobanana-adc のリリースをこのセッションで直接実行する。引数 $ARGUMENTS で バージョンを指定できる:

  • /release — コミット履歴から自動判定
  • /release 0.9.0 — 指定バージョンで固定

コード変更や設計判断を伴わない運用作業なので、サブエージェントは spawn せず Bash で順に実行する。失敗したステップだけをやり直せばよい。

0. Preflight

claude plugin validate . || { echo "plugin validate failed; aborting" >&2; exit 1; }

PKG=$(node -p "require('./package.json').version")
PLUGIN=$(node -p "require('./.claude-plugin/plugin.json').version")
MARKET=$(node -p "require('./.claude-plugin/marketplace.json').plugins.find(p => p.name === 'nanobanana-adc').version")
CLI=$(grep -oE "CLI_VERSION = '[^']+'" src/cli.ts)
echo "versions — package=$PKG plugin=$PLUGIN marketplace=$MARKET cli=$CLI"

npm run typecheck && npm test && npm run build

4 つのバージョンが揃っていない場合は、後続のバンプで 4 箇所すべてを更新すること。 CI の validate-plugin ジョブでも同じ整合性チェックが走る。

作業ツリーに未コミットの変更が残っていないことも確認する。リリースコミットは CHANGELOG とバージョンファイルしか含めないため、機能変更が未コミットのままだと そのタグには入らない。

1. バージョンを判定

CURRENT=$(node -p "require('./package.json').version")
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
git log ${LAST_TAG:+${LAST_TAG}..}HEAD --oneline

引数指定があればそれを採用。無ければ Conventional Commits で判定する:

キーワード 変更レベル
BREAKING CHANGE, !: major
feat:, feat( minor
fix: / chore: / docs: のみ patch

最も大きい変更レベルを採用する。

2. CHANGELOG.md を更新

## [Unreleased] ブロックがあれば ## [X.Y.Z] - YYYY-MM-DD(実行日)に書き換える。 無ければタイトル直下に新しいブロックを追加する:

## [X.Y.Z] - YYYY-MM-DD

### Added / ### Changed / ### Fixed

分類は feat: → Added / fix: → Fixed / それ以外 → Changed。コミットメッセージを そのままコピーせず、ユーザーが読んで意味がわかる説明に書き直す。

3. バージョンを 4 箇所に反映

NEW_VERSION=X.Y.Z
node -e "const p=require('./package.json'); p.version='${NEW_VERSION}'; require('fs').writeFileSync('package.json', JSON.stringify(p,null,2)+'\n')"
node -e "const p=require('./.claude-plugin/plugin.json'); p.version='${NEW_VERSION}'; require('fs').writeFileSync('.claude-plugin/plugin.json', JSON.stringify(p,null,2)+'\n')"
node -e "const m=require('./.claude-plugin/marketplace.json'); m.plugins.find(p=>p.name==='nanobanana-adc').version='${NEW_VERSION}'; require('fs').writeFileSync('.claude-plugin/marketplace.json', JSON.stringify(m,null,2)+'\n')"
sed -i '' "s/^const CLI_VERSION = '.*';/const CLI_VERSION = '${NEW_VERSION}';/" src/cli.ts

npm run typecheck && npm test && npm run build && ./bin/nanobanana-adc --version

Read the full file on GitHub · 134 lines

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. 10d ago First seen · 134 lines · 31 tokens per session scan A a7a179dd96f6

Subscribe to this mod's changes

release is a command published in the GitHub repository hummer98/nanobanana-adc (4 stars, last pushed 22d ago), licensed MIT. It adds 31 tokens to every session and 1,488 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.