A release checklist for plugins in a marketplace. It reviews changed code, checks version numbers, verifies consistency, and pushes the result to GitHub.

Use it when preparing plugin updates for release. It guides code review, version checks, consistency checks, and the GitHub push.

It helps catch bugs, security concerns, and mismatched versions before publishing changes. It also makes clear which plugins were changed.

release — Skill for Claude Code by ai-native-sys/claude-code-tools

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.

Any agent

npx skills add ai-native-sys/claude-code-tools --skill release

Clone the repo

git clone --depth 1 https://github.com/ai-native-sys/claude-code-tools

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ai-native-sys/claude-code-tools/release/github.svg)](https://agentmods.dev/skills/ai-native-sys/claude-code-tools/release)

Your own site

<a href="https://agentmods.dev/skills/ai-native-sys/claude-code-tools/release"><img src="https://agentmods.dev/badge/skills/ai-native-sys/claude-code-tools/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ai-native-sys/claude-code-tools/release"><img src="https://agentmods.dev/badge/skills/ai-native-sys/claude-code-tools/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 576 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.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.00576
Opus 5.5	$0.00007	$0.00230
Sonnet 5.5	$0.00004	$0.00115
Haiku 4.5	$0.00002	$0.00058

Measured 2mo ago against content hash ddfbcc3e4668, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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/skills/release/SKILL.md · 62 lines

How it starts

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

Release Plugins

Guide the release process for this plugin marketplace: review changes, bump versions, verify consistency, and push to GitHub.

Step 1: Code review current changes

Run git diff main (or git diff HEAD if on main with uncommitted changes) to identify all changed files.

Review the changes for:

Correctness and code quality
Potential bugs or regressions
Security concerns

Summarize findings to the user. If there are significant issues, flag them and ask if the user wants to proceed or fix first.

Step 2: Identify changed plugins

From the diff, determine which plugins under plugins/ have been modified. A plugin is considered changed if any file under its plugins/<name>/ directory was modified.

List the changed plugins for the user.

Step 3: Check and bump version numbers

For each changed plugin, check whether its version has already been bumped by comparing:

plugins/<name>/.claude-plugin/plugin.json → version field
.claude-plugin/marketplace.json → the matching entry in plugins[] → version field

If the version has NOT been updated for a changed plugin, ask the user what the new version number should be (suggest a semver bump based on the nature of the changes — patch for fixes, minor for features, major for breaking changes).

Only update versions for plugins that have actual changes. Do NOT touch versions for unchanged plugins.

Step 4: Update version numbers

Apply the new version to both locations for each changed plugin:

plugins/<name>/.claude-plugin/plugin.json → version
.claude-plugin/marketplace.json → the matching plugins[] entry → version

Step 5: Verify version consistency

For every plugin listed in .claude-plugin/marketplace.json, verify that:

The version in marketplace.json matches the version in plugins/<name>/.claude-plugin/plugin.json
The name fields match
The plugin source directory exists

Report any mismatches and fix them before proceeding.

Step 6: Commit and push

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

2mo ago First seen · 62 lines · 18 tokens per session scan A ddfbcc3e4668

Subscribe to this mod's changes

release is a skill published in the GitHub repository ai-native-sys/claude-code-tools (1 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 576 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.

Git and workflow Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

release