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/akiojin/unity-mcp-server/releasegit clone --depth 1 https://github.com/akiojin/unity-mcp-serverWhat 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.00046 | $0.02154 |
| Opus 5 | $0.00023 | $0.01077 |
| Sonnet 5 | $0.00009 | $0.00431 |
| Haiku 4.5 | $0.00005 | $0.00215 |
Grade A, and why
release 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release コマンド
LLMベースのインタラクティブリリースフローです。developブランチでのみ実行可能です。
前提条件チェック
以下を確認してください:
- developブランチであること:
develop以外のブランチでは実行不可 - クリーンな状態: ワーキングディレクトリに未コミットの変更がないこと
- リモート同期: developブランチがリモートと同期していること
# 現在のブランチを確認
CURRENT_BRANCH=$(git branch --show-current)
# developブランチかチェック
if [ "$CURRENT_BRANCH" != "develop" ]; then
echo "❌ エラー: /release コマンドは develop ブランチでのみ実行可能です"
echo "現在のブランチ: $CURRENT_BRANCH"
echo ""
echo "以下の手順でdevelopブランチに移動してください:"
echo " git checkout develop"
exit 1
fi
# ワーキングディレクトリの状態を確認
git status --porcelain
# タグを取得
git fetch --tags origin
developブランチでない場合、または未コミットの変更がある場合はエラーメッセージを表示して中止してください。
Phase 1: 変更分析
最新のタグから現在のHEADまでの変更を分析します。
# 最新タグを取得
git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0"
# タグからの変更履歴を取得
git log $(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0")..HEAD --oneline
# 変更ファイルの統計
git diff $(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0")..HEAD --stat
変更サマリーの生成
コミットログを分析し、以下の形式で日本語のサマリーを生成:
## 変更サマリー
### 新機能
- [feat: xxx] の説明
### バグ修正
- [fix: xxx] の説明
### 改善
- [perf: xxx] の説明
### その他
- [chore: xxx] の説明
Phase 2: バージョン判定
コミットメッセージを分析してsemverを決定:
| 検出内容 | バージョン変更 | 用途 |
|---|---|---|
BREAKING CHANGE: または feat!: |
major (X.0.0) | ユーザー向け破壊的変更 |
feat: |
minor (x.Y.0) | ユーザー向け新機能のみ |
fix:, perf: |
patch (x.y.Z) | バグ修正、性能改善 |
chore:, refactor:, ci:, build:, docs:, test: |
なし | 内部的な変更 |
コミットタイプの使い分け（重要）
feat: はユーザー向け新機能のみに使用。内部的な変更には適切なタイプを使う:
| 変更内容 | 正しいタイプ | 誤ったタイプ |
|---|---|---|
| /releaseコマンド改善 | chore(release): |
feat(release): |
| プラグイン構造変更 | refactor(plugin): |
feat(plugin): |
| CI/Docker設定 | ci: / chore(docker): |
feat(ci): |
| 依存関係更新 | chore(deps): |
feat(deps): |
| テスト追加 | test: |
feat(test): |
| スキル設定変更 | chore(skill): |
feat(skill): |
ユーザー向け新機能の例（feat: を使用）
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 · 258 lines · 46 tokens per session scan A 7d410aaefe37
release is a command published in the GitHub repository akiojin/unity-mcp-server (34 stars, last pushed 9d ago), licensed MIT. It adds 46 tokens to every session and 2,154 once invoked, about $0.0002 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 commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
Command "release" from shenjingnan/xiaozhi-client, covering release command, 执行步骤, 发布流程, 版本规范 and 配置文件.