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.
npx agentmods add skills/ayutaz/piper-plus/release-prepnpx skills add ayutaz/piper-plus --skill release-prepgit clone --depth 1 https://github.com/ayutaz/piper-plusWrote 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.
[](https://agentmods.dev/skills/ayutaz/piper-plus/release-prep)<a href="https://agentmods.dev/skills/ayutaz/piper-plus/release-prep"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/release-prep.svg" alt="Measured on agentmods" height="20"></a>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.00079 | $0.02317 |
| Opus 5 | $0.00039 | $0.01158 |
| Sonnet 5 | $0.00016 | $0.00463 |
| Haiku 4.5 | $0.00008 | $0.00232 |
Grade A, and why
release-prep 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 4d 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(curl -s *) Bash(npm view *) Bash(git diff *) Bash(git log *) Bash(git status *) Bash(rg *) Read Edit Grep How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Preparation Helper
リリース作業の forensic check と CHANGELOG 移行支援 を 1 つにまとめた skill。手動でやると忘れがちな以下 4 段階を 1 コマンドで通す:
- 各 manifest の 現在の version を一覧化 (7 runtime × 9 manifest)
release-versions.tomlのexpected_prefixとの照合- CHANGELOG.md
[Unreleased]の内容と、リリース時に必要な 昇格作業 の提案 - 公開 registry (PyPI / crates.io / NuGet / npm / Maven Central) の 最新公開 version 取得
実装は read-mostly — 変更提案は markdown diff 形式でユーザに提示し、 適用は明示確認後 (memory feedback_merge_caution.md に従う)。
引数
$ARGUMENTS空: 全 runtime を一覧python/rust/csharp/npm/swift/kotlin: 特定 runtime のみ--target-version X.Y.Z: 次回リリース予定 version (CHANGELOG 移行提案に使う)
現在の状態
- ブランチ: !
git rev-parse --abbrev-ref HEAD - 引数: $ARGUMENTS
- canonical truth: !
grep -A1 "^\\[meta\\]" docs/spec/release-versions.toml | head -5
フェーズ 1: Manifest version 一覧
以下の 9 manifest を並列で Read し、現在の version を抽出して表化:
| Runtime | Manifest | 抽出キー |
|---|---|---|
| Python (PyPI) | VERSION |
ファイル全体 |
| Rust (crates.io) | src/rust/Cargo.toml |
[workspace.package].version |
| C# Core (NuGet) | src/csharp/PiperPlus.Core/PiperPlus.Core.csproj |
<Version> |
| C# Cli (NuGet) | src/csharp/PiperPlus.Cli/PiperPlus.Cli.csproj |
<Version> |
| npm synthesis | src/wasm/openjtalk-web/package.json |
.version |
| npm g2p | src/wasm/g2p/package.json |
.version |
| Swift synthesis | Package.swift |
let version = 行 |
| Swift G2P | Package.swift |
let g2pVersion = 行 |
| Kotlin Android | android/gradle.properties |
VERSION_NAME= |
# 例: rust workspace version
grep -A1 "^\[workspace.package\]" src/rust/Cargo.toml | grep "^version" | head -1
フェーズ 2: Expected prefix との照合
docs/spec/release-versions.toml を tomllib で読み、各 manifest の expected_prefix を取得。フェーズ 1 の実 version が prefix で始まるかを照合:
| Runtime | Manifest version | expected_prefix | Status |
|---------|------------------|-----------------|--------|
| Python | 1.12.0 | 1.12. | ✓ |
| Rust | 0.4.0 | 0.4. | ✓ |
| C# Core | 0.3.0 | 0.3. | ✓ |
| ... | ... | ... | ... |
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.
- 4d ago First seen · 183 lines · 79 tokens per session scan A dd7b81e4fe3b
release-prep is a skill published in the GitHub repository ayutaz/piper-plus (202 stars, last pushed 7d ago), licensed MIT. It adds 79 tokens to every session and 2,317 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
model-integration
Use when adding a new model or pipeline to diffusers, setting up file structure for a new model, converting a pipeline to modular format, or converting weights for a new version of an already-supported model.
custom-blocks
Use when the user has written (or wants to write) a ModularPipelineBlocks subclass in a local Python file and needs to package it into a Hub-uploadable directory. Covers the workflow from a single block.py file to a published custom-block repo that consumers can load via ModularPipeline.frompretrained( …
diffusers-cli
Use when the user wants to run a diffusers pipeline from a terminal (one-off generation, batch jobs, smoke-testing a new model), run on HF Sandbox hardware via --remote, introspect a pipeline's input schema before calling it, or attach a LoRA at inference time. Prefer this over writing ad-hoc Python scripts for…
self-review
Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the @claude CI (checks the diff against references/review-rules.md, traces call paths for dead code). Reports findings grouped by severity, flagging what to fix before submitting (blocking issues + dead code)…
hf-release-notes
Generate Hugging Face Hub (huggingfacehub) release notes from cached PR JSON files. Use when asked to draft release notes from PR files.
physicsnemo-shard-tensor
Official NVIDIA-authored guidance for PhysicsNeMo ShardTensor domain parallelism — integrate domain parallelism into training/inference scripts (new or existing) with DDP or FSDP2, write and register shard patches to enable new layers/ops, and bootstrap multi-GPU correctness tests. Use when working with ShardTensor…