piper-plus: Skill for Claude Code

.claude/skills/precheck/SKILL.md

precheck is a skill for Claude Code from ayutaz/piper-plus. It costs 50 tokens per session (1,062 once invoked), scanned A, original, MIT.

A pre-release command guide that runs formatting, code-quality checks, builds, and tests for the parts of a multilingual text-to-speech project that changed.

In plain words
What is it for?
Use it before opening a pull request to check Python, Rust, C#, Go, JavaScript, or C++ changes, either by naming a language or detecting the scope from the Git changes.
Why use it?
It catches style errors, build failures, and broken tests before a pull request or continuous-integration check does.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

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 reads a path above its own folder, which exists only inside the repository. The line is cd src/python_run && uv run pytest tests/ -o addopts="" --tb=short -q && cd ../...

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/precheck/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 precheck

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/ayutaz/piper-plus/precheck"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/precheck.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,062 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
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.00050 $0.01062
Opus 5.5 $0.00020 $0.00425
Sonnet 5.5 $0.00010 $0.00212
Haiku 4.5 $0.00005 $0.00106

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

Security

Grade A, and why

precheck 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/skills/precheck/SKILL.md · 114 lines

How it starts

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

Pre-commit / Pre-PR チェック

$ARGUMENTS で指定されたスコープに対して、CI が実行するチェックと同等の検査をローカルで実行します。

変更ファイル

!git diff --name-only HEAD 2>/dev/null | head -30

スコープ判定

引数 $ARGUMENTS:

  • python → src/python/ + src/python_run/ (ruff は CI と同じく repo 全体の .py が対象。 scripts/ / tests/ / docker/ 等の変更も python scope とみなす)
  • rust → src/rust/ のみ
  • cs → src/csharp/ のみ
  • go → src/go/ のみ
  • js → src/wasm/openjtalk-web/ のみ
  • cpp → src/cpp/ のみ
  • all → 全ランタイム
  • (空) → 上記の git diff の結果からスコープを推定 (複数該当ならそれら全て)

実行ステップ (該当スコープのみ)

Python

# Lint (CI の lint-gates.yml python-lint step と同じく repo 全体。 除外は pyproject.toml の [tool.ruff])
uv run ruff check

# Format check
uv run ruff format --check

# Unit tests (runtime + g2p)
cd src/python_run && uv run pytest tests/ -o addopts="" --tb=short -q && cd ../..

Rust

cd src/rust
cargo fmt --all -- --check
cargo clippy --workspace --all-features -- -D warnings
cargo test -p piper-plus --no-fail-fast
cd ../..

C# (.NET)

dotnet build src/csharp/PiperPlus.sln -c Release --nologo
dotnet format src/csharp/PiperPlus.sln --verify-no-changes --no-restore
dotnet test src/csharp/PiperPlus.sln -c Release --no-build --nologo --verbosity minimal

Go

cd src/go
go vet ./... ./phonemize/...
go test -race -count=1 ./... ./phonemize/...
cd ../..

JavaScript / WASM

cd src/wasm/openjtalk-web
npm run test:npm-package:all
cd ../../..

C++

cmake --build build --config Release
ctest --test-dir build -C Release --output-on-failure

報告フォーマット

各ステップ完了後、以下の形式で結果を報告:

## Precheck 結果

| ステップ | 結果 | 詳細 |
|---------|------|------|
| Python ruff check | ✅ / ❌ | (失敗時はエラー要約) |
| Python ruff format | ✅ / ❌ | |
| Python pytest | ✅ / ❌ | (passed/failed/skipped カウント) |
| ... | ... | ... |

失敗時の対応

  • ruff format 失敗 → uv run ruff format で自動修正
  • ruff check 失敗 → uv run ruff check --fix で自動修正
  • pytest 失敗 → 失敗テストの最初の 3 件を要約して原因候補を提示
  • dotnet format 失敗 → dotnet format src/csharp/PiperPlus.sln で自動修正

Read the full file on GitHub · 114 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 5028ba070c5e
  2. 2mo ago First seen · 114 lines · 50 tokens per session scan A cdef24c99c19

Subscribe to this mod's changes

precheck is a skill published in the GitHub repository ayutaz/piper-plus (239 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,062 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

quality-scan

Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.

diegosouzapw/OmniRoute · 45 tokens

e2e-testing

Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.

thedaviddias/Front-End-Checklist · 38 tokens

mirrord-prev-env

Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…

metalbear-co/mirrord · 122 tokens

test-setup

Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.

Donchitos/Claude-Code-Game-Studios · 32 tokens

ci

Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…

onsi/ginkgo · 151 tokens

testing-and-ci

Choose and run unit, E2E, Caddyfile fixture, automation, and CI checks for caddy-security. Use for coverage requirements, test evidence, failures, and report workflows; official OP conformance remains opt-in.

greenpau/caddy-security · 50 tokens