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 commands/kaze-jp/kusa/releasegit clone --depth 1 https://github.com/kaze-jp/kusaWhat 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.00021 | $0.00831 |
| Opus 5 | $0.00010 | $0.00415 |
| Sonnet 5 | $0.00004 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade C, and why
release scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
cd /tmp && rm -rf homebrew-tap-update && gh repo clone kaze-jp/homebrew-tap homebrew-tap-update How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kusa Release
新しいバージョンをリリースする。引数でバージョンを指定（例: /release 0.4.0）。
引数がない場合は、直近の変更内容から semver を判断してユーザーに提案する。
手順
1. バージョン bump
以下の 3ファイル のバージョンを更新:
package.json→"version": "X.Y.Z"src-tauri/tauri.conf.json→"version": "X.Y.Z"src-tauri/Cargo.toml→version = "X.Y.Z"
2. CHANGELOG.md 更新
CHANGELOG.md の先頭に新しいセクションを追加。
git log で前バージョンからの変更を確認し、Added / Fixed / Changed に分類して記載。
末尾のリンク一覧にも新バージョンを追加。
3. コミット + PR マージ
git checkout -b release/X.Y.Z
git add package.json src-tauri/tauri.conf.json src-tauri/Cargo.toml CHANGELOG.md
git commit -m "chore: bump version to X.Y.Z"
git push -u origin release/X.Y.Z
gh pr create --title "chore: bump version to X.Y.Z" --body "Release X.Y.Z"
gh pr merge --merge
git checkout main && git pull origin main
4. Tauri ビルド
bun run tauri build
成功すると以下が生成される:
src-tauri/target/release/bundle/macos/kusa.appsrc-tauri/target/release/bundle/dmg/kusa_X.Y.Z_aarch64.dmg
ビルドで Cargo.lock や src-tauri/gen/schemas/ が変更された場合は、ブランチを作って追加コミット → PR → マージ → main に戻る。
5. GitHub Release 作成
gh release create vX.Y.Z \
src-tauri/target/release/bundle/dmg/kusa_X.Y.Z_aarch64.dmg \
--title "vX.Y.Z" \
--notes "$(cat <<'EOF'
CHANGELOG.md の該当セクションの内容をここに貼る
EOF
)"
6. Homebrew tap 更新
# DMG の sha256 を取得
shasum -a 256 src-tauri/target/release/bundle/dmg/kusa_X.Y.Z_aarch64.dmg
# tap リポジトリをクローン（/tmp に）
cd /tmp && rm -rf homebrew-tap-update && gh repo clone kaze-jp/homebrew-tap homebrew-tap-update
# Casks/kusa.rb の version と sha256 arm: を更新
# version "X.Y.Z"
# sha256 arm: "新しいsha256"
# コミット + push
cd /tmp/homebrew-tap-update
git add Casks/kusa.rb
git commit -m "chore: update kusa cask to vX.Y.Z"
git push origin main
7. ローカル更新
brew reinstall kaze-jp/tap/kusa
kusa --version # → kusa X.Y.Z
注意事項
git commit --no-verify禁止- Conventional Commits 形式 (
chore: bump version to X.Y.Z) Co-Authored-By: Claude Opus 4.6 <[email protected]>をコミットに付与
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 · 95 lines · 21 tokens per session scan C 5d4bacf7bf69
release is a command published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 831 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.