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/run-testsnpx skills add ayutaz/piper-plus --skill run-testsgit 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/run-tests)<a href="https://agentmods.dev/skills/ayutaz/piper-plus/run-tests"><img src="https://agentmods.dev/badge/skills/ayutaz/piper-plus/run-tests.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.00052 | $0.01044 |
| Opus 5 | $0.00026 | $0.00522 |
| Sonnet 5 | $0.00010 | $0.00209 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
run-tests 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
piper-plus テスト実行
各言語ランタイムのテストを CI と同じ条件でローカル実行します。
変更ファイル
!git diff --name-only HEAD 2>/dev/null | head -20
ターゲット選択
$ARGUMENTS:
python→ Python 全体rust→ Rust workspacecs→ .NET solutiongo→ Go modulejs→ JS/WASM (npm-package)cpp→ C++ (cmake build + ctest)all→ 上記すべて (順次、失敗しても次に進む)- (空) →
git diff HEADの結果から判定 (複数該当ならそれら全部)
各ターゲットの実行コマンド
Python
cd src/python_run
uv run pytest tests/ -o addopts="" -v --tb=short
cd ../..
# G2P 単体テスト (もし対象なら)
cd src/python/g2p
uv run pytest -o addopts="" -v --tb=short
cd ../../..
注意:
- pytest.ini の
--covを-o addopts=""で上書き (pytest-cov が無い環境向け) - 学習・ベンチマーク系テストは除外 (
-m "unit and not training and not benchmark"も可)
Rust
cd src/rust
cargo test -p piper-plus --no-fail-fast
cargo test -p piper-plus --features naist-jdic --no-fail-fast
cd ../..
C# (.NET)
dotnet test src/csharp/PiperPlus.sln -c Release --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++
# Build がまだなら先にビルド
if [ ! -f build/CMakeCache.txt ]; then
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=ON
fi
cmake --build build --config Release
ctest --test-dir build -C Release --output-on-failure
結果報告
各ターゲット完了後、以下の形式で報告:
## テスト実行結果
| ランタイム | Pass | Fail | Skip | 時間 |
|----------|------|------|------|------|
| Python (pytest) | 212 | 0 | 20 | 22s |
| Rust (cargo test) | 145 | 0 | 0 | 1m |
| ... | ... | ... | ... | ... |
### 失敗詳細
(失敗があった場合のみ、最初の 3 件まで)
- `test_xxx` (ファイル:行): エラー要約
失敗時のヒント
- Python ImportError →
uv syncで依存をインストール - Rust feature not found →
cargo buildで先にビルドを通す - C# build failed →
dotnet restore src/csharp/PiperPlus.slnを実行 - WASM ImportError →
cd src/wasm/openjtalk-web && npm install - C++ ctest failed →
cmake --build build --verboseでビルドエラーを再確認
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.
- 5d ago First seen · 125 lines · 52 tokens per session scan A 6903126046f6
run-tests is a skill published in the GitHub repository ayutaz/piper-plus (202 stars, last pushed 7d ago), licensed MIT. It adds 52 tokens to every session and 1,044 once invoked, about $0.0003 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.
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…