piper-plus: Skill for Claude Code

.claude/skills/prepare-release/SKILL.md

prepare-release is a skill for Claude Code from ayutaz/piper-plus. It costs 95 tokens per session (3,274 once invoked), scanned A, original, MIT.

A release-preparation checker for nine packages and five package registries, which are services that distribute software packages. It prepares version changes, lockfile updates, Swift checksums, change-log edits, publishing order, and post-release checks.

In plain words
What is it for?
Use it to prepare a Python, Rust, C#, npm, Swift, or Kotlin release at a chosen version. It can produce a dry-run plan or, with the apply option, make the version updates after confirmation.
Why use it?
It reduces mistakes when one release version is written in many files and packages depend on one another. By default it shows a proposed change without editing files or publishing anything.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is ayutaz/piper-plus's own configuration. It tells Claude Code how to work on piper-plus itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything piper-plus configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is uv run python scripts/check_voice_catalog_parity.py 2>&1 | tail -3.

Reuse

Borrowing it

Nothing to install: this file belongs to ayutaz/piper-plus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ayutaz/piper-plus/dev/.claude/skills/prepare-release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ayutaz/piper-plus

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.

agentmods badge for prepare-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/ayutaz/piper-plus/prepare-release/github.svg)](https://agentmods.dev/skills/ayutaz/piper-plus/prepare-release)
Your own site
<a href="https://agentmods.dev/skills/ayutaz/piper-plus/prepare-release"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/prepare-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 prepare-release

Your own site · 80×15
<a href="https://agentmods.dev/skills/ayutaz/piper-plus/prepare-release"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/prepare-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,274 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Data Exfiltration · line 163
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
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.00095 $0.03274
Opus 5.5 $0.00038 $0.01310
Sonnet 5.5 $0.00019 $0.00655
Haiku 4.5 $0.00010 $0.00327

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

Security

Grade A, and why

prepare-release scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

allowed-tools: Bash(cat *) Bash(grep *) Bash(jq *) Bash(rg *) Bash(awk *) Bash(curl -s *) Bash(npm view *) Bash(git diff *) Bash(git log *) Bash(git status *) Bash(swift package compute-checksum *) Read Edit Grep
.claude/skills/prepare-release/SKILL.md · 201 lines

How it starts

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

Release Preparation Skill (Bump 適用版)

release-prep (read-mostly な確認) の続きとして、 実際の version bump 差分 を全 manifest にわたり生成する skill。

ユーザは memory feedback_conservative_changes.md / feedback_merge_caution.md に従い、 適用は明示確認を取ってから (デフォルト dry-run、 markdown diff 提示のみ)。

カバー範囲

段階 対応
Version 散在検出 9 manifest を一括 bump 案として markdown 出力
Lockfile 再生成 uv.lock / Cargo.lock / package-lock.json の更新コマンド提示
Swift checksum xcframework artifact 取得後の swift package compute-checksum 手順
CHANGELOG 昇格 [Unreleased] → [X.Y.Z] - YYYY-MM-DD の markdown diff
Tag 順序ガイド 独立パッケージ tag (npm は g2p 先行) → docker-v → v tag → Manual Release dispatch の順序
公開後検証 各 registry で publish 完了確認の手順

引数

  • $ARGUMENTS 1 つ目: all / python / rust / csharp / npm / swift / kotlin
  • --target-version X.Y.Z: 次回リリース version (必須)
  • --dry-run (default): markdown 出力のみ、 ファイル変更しない
  • --apply: dry-run の確認後にユーザが追加で渡す flag。 これがある時のみ Edit を実行

現在の状態

  • ブランチ: !git rev-parse --abbrev-ref HEAD
  • 引数: $ARGUMENTS
  • 直近 tag: !git tag --sort=-v:refname | head -3

フェーズ 1: 現 manifest version 読み出し (9 ファイル)

並列で Read し、 各 manifest の現 version を抽出:

Runtime Manifest 抽出キー
Python VERSION ファイル全体
Python (g2p) src/python/g2p/pyproject.toml [project].version
Rust src/rust/Cargo.toml [workspace.package].version
C# Core src/csharp/PiperPlus.Core/PiperPlus.Core.csproj <Version>
C# Cli src/csharp/PiperPlus.Cli/PiperPlus.Cli.csproj <Version>
npm synth src/wasm/openjtalk-web/package.json .version
npm g2p src/wasm/g2p/package.json .version
Swift Package.swift let version = 行 + let g2pVersion = 行
Kotlin android/gradle.properties VERSION_NAME=

フェーズ 2: 既存 sync gate との交差確認

uv run python scripts/check_voice_catalog_parity.py 2>&1 | tail -3
uv run python scripts/check_ort_versions.py 2>&1 | tail -3
uv run python scripts/check_openjtalk_version_sync.py 2>&1 | tail -3
uv run python scripts/check_ruff_version_sync.py 2>&1 | tail -3
uv run python scripts/check_migration_changelog_parity.py 2>&1 | tail -3

Read the full file on GitHub · 201 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. 3d ago Changed · +4 lines 76c2c04bb83e
  2. 14d ago Changed 17cf3d84d4d0
  3. 2mo ago First seen · 197 lines · 95 tokens per session scan A a6e4dfbd808c

Subscribe to this mod's changes

prepare-release is a skill published in the GitHub repository ayutaz/piper-plus (239 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 3,274 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.