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/sync-docsnpx skills add ayutaz/piper-plus --skill sync-docsgit clone --depth 1 https://github.com/ayutaz/piper-plusWhat 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.00061 | $0.02659 |
| Opus 5 | $0.00030 | $0.01329 |
| Sonnet 5 | $0.00012 | $0.00532 |
| Haiku 4.5 | $0.00006 | $0.00266 |
Grade A, and why
sync-docs 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 2d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ドキュメント同期 (エージェントチーム並列監査)
コード変更に対して CLAUDE.md / README / CHANGELOG / docs/features / docstring を一括で監査し、更新が必要な箇所を検出して自動適用します。
前提
このスキルは コミット前 に使うことを想定しています。コミット済みの変更と未ステージ変更の両方を対象にします。
入力
$ARGUMENTSが空:dev..HEAD(現在のブランチの全変更) + 未コミット変更$ARGUMENTS=staged: ステージ済み変更のみ (git diff --cached)$ARGUMENTS=HEAD~3..HEAD: 特定のコミット範囲$ARGUMENTS= ファイルパス: そのファイルの変更のみ
現在の状態
- ブランチ: !
git rev-parse --abbrev-ref HEAD - dev との差分ファイル数: !
git diff --name-only dev..HEAD 2>/dev/null | wc -l | tr -d ' ' - 未コミット変更: !
git status --short 2>/dev/null | wc -l | tr -d ' '
フェーズ 1: 変更サマリ収集
-
git diff --name-onlyで変更ファイルをカテゴリ分類:- 実装 (
src/python_run/piper_plus/*.py,src/python/g2p/**,src/rust/piper-core/**,src/cpp/*.cpp,src/csharp/**,src/go/**,src/wasm/openjtalk-web/src/*.js) - テスト (
*/tests/**,*/test/**) - ビルド (
*.toml,*.json,CMakeLists.txt,*.yml) - ドキュメント (
*.md,docs/**)
- 実装 (
-
各カテゴリのファイル数と代表ファイルを記録
フェーズ 2: 並列ドキュメント監査 (エージェントチーム)
以下の 7 エージェントを 1 メッセージで並列起動 します:
Agent 1: CLAUDE.md 監査
subagent_type: Explore
task: CLAUDE.md の「実装済み機能」「重要なファイルパス」「OpenAI 互換 API」セクションを確認し、実装変更に対する追加・修正が必要か判定。新規モジュール/クラス/HTTP エンドポイント/テストファイルが未記載なら、具体的な diff を提案。
Agent 2: ルート README 監査
subagent_type: Explore
task: README.md, README_EN.md, README.*.md (他言語) の Features / Interfaces / Feature Support Matrix を確認。新機能が各ランタイムで利用可能になった場合、対応 runtime 行を更新。
Agent 3: ランタイム別 README 監査
subagent_type: Explore
task: src/python_run/README.md, src/python_run/README_http.md, src/wasm/openjtalk-web/README.md, src/wasm/openjtalk-web/README.npm.md, src/rust/piper-cli/README.md, src/go/README.md を確認。API 例・CLI フラグ・HTTP エンドポイントが最新か判定。
Agent 4: CHANGELOG 監査
subagent_type: Explore
task: CHANGELOG.md と src/wasm/openjtalk-web/CHANGELOG.md の [Unreleased] セクションが、コード変更 (新機能/バグ修正/破壊的変更) を反映しているか確認。未反映なら具体的な markdown を提案。
Agent 5: docs/features・docs/spec 監査
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.
- 2d ago First seen · 168 lines · 61 tokens per session scan A 13b01c62ffa8
sync-docs is a skill published in the GitHub repository ayutaz/piper-plus (202 stars, last pushed 5d ago), licensed MIT. It adds 61 tokens to every session and 2,659 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…