A release command for the whetstone plugin that handles version updates, commits, pushes, mirroring, and local plugin updates. Versioning records which release of the plugin is installed.

Reviewing changes since the previous release, choosing a major, minor, or patch version increase, updating the changelog, and publishing the release.

It gathers changes and performs the release steps in one workflow, reducing the chance of forgetting version or changelog work.

release — Command by iliaal

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/iliaal/whetstone/release

Clone the repo

git clone --depth 1 https://github.com/iliaal/whetstone

Made for: Claude Code.

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,169 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.

Model	Per session	Once invoked
Fable 5	$0.00020	$0.02169
Opus 5	$0.00010	$0.01085
Sonnet 5	$0.00004	$0.00434
Haiku 4.5	$0.00002	$0.00217

Measured 3d ago against content hash 7909907cb58a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

.claude/commands/release.md · 95 lines

How it starts

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

Release

Run the full release pipeline for the whetstone plugin. This command owns all version ceremony — per-change edits do NOT bump versions or touch CHANGELOG.md. Those steps happen here, once, summarizing everything that accumulated since the last release.

Phase 1: Survey what changed since the last release

Find the current version in plugins/whetstone/.claude-plugin/plugin.json.
Run git log v<current-version>..HEAD --oneline (fallback: git log --since="<last release date>" --oneline) to list commits since the last tag.
Run git diff v<current-version>..HEAD --stat to see which files changed.
Classify the changes into added/changed/fixed/removed buckets per Keep a Changelog. Scan specifically for:
- New files under plugins/whetstone/{skills,agents,commands}/ → Added
- Deletions under the same paths → Removed
- Edits to existing components → Changed
- Commits with fix: prefix or bug-fix language → Fixed

Phase 2: Decide the semver bump

MAJOR if any breaking change (component removed, renamed, frontmatter contract changed)
MINOR if any new skill, agent, or command was added
PATCH otherwise (edits, doc updates, trigger-pattern tweaks)

Ask the user to confirm the bump type before writing anything, and offer a short rationale.

Phase 3: Apply the bump

Update version in plugins/whetstone/.claude-plugin/plugin.json, plugins/whetstone/.codex-plugin/plugin.json, and .claude-plugin/marketplace.json. All three must match.
Prepend a new CHANGELOG.md entry with today's date, the new version, a one-line summary, and buckets of commits grouped under ### Added / ### Changed / ### Fixed / ### Removed. Use the writing skill to polish the tone before committing.
Run bash scripts/update-metadata.sh to sync component counts into plugin.json and marketplace.json descriptions.
Verify README.md agent/command/skill counts and tables still match reality — update if drift.
Validate JSON: jq . .claude-plugin/marketplace.json .agents/plugins/marketplace.json plugins/whetstone/.claude-plugin/plugin.json plugins/whetstone/.codex-plugin/plugin.json plugins/whetstone/.mcp.json.

Read the full file on GitHub · 95 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.

3d ago First seen · 95 lines · 20 tokens per session scan A 7909907cb58a

Subscribe to this mod's changes

release is a command published in the GitHub repository iliaal/whetstone (32 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 2,169 once invoked, about $0.0001 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-30.

Git and workflow Releases agent-skills ai-agents ai-tools claude-code claude-code-plugin

release

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Release

Phase 1: Survey what changed since the last release

Phase 2: Decide the semver bump

Phase 3: Apply the bump

What this file has done since we first saw it

Other commands, from other repositories

release

release

release

bump

ship-ticket

generate-changelog