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.
git clone --depth 1 https://github.com/akiojin/unity-mcp-serverWrote 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/commands/akiojin/unity-mcp-server/implement)<a href="https://agentmods.dev/commands/akiojin/unity-mcp-server/implement"><img src="https://agentmods.dev/badge/commands/akiojin/unity-mcp-server/implement/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.
<a href="https://agentmods.dev/commands/akiojin/unity-mcp-server/implement"><img src="https://agentmods.dev/badge/commands/akiojin/unity-mcp-server/implement.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00034 | $0.00906 |
| Opus 5.5 | $0.00014 | $0.00362 |
| Sonnet 5.5 | $0.00007 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
implement 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 1mo 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.
What it actually says
ユーザー入力
$ARGUMENTS
空でない場合、続行する前にユーザー入力を考慮する必要があります。
目的
tasks.md に定義されたタスクを順次実行し、機能を実装する。
実行手順
1. コンテキスト初期化
{SCRIPT} を実行し、FEATURE_DIR と AVAILABLE_DOCS を取得(パスはすべて絶対パス)。
2. チェックリスト検証
FEATURE_DIR/checklists/ が存在する場合:
- 各チェックリストファイルをスキャン
- 未完了項目(
- [ ])をカウント - 未完了がある場合は停止して確認:
以下のチェックリストに未完了項目があります: - requirements.md: 3件未完了 - security.md: 1件未完了 続行しますか? (yes/no) - ユーザーが
noなら中断
3. ドキュメント読み込み
必須:
- tasks.md(タスクリスト)
- plan.md(技術スタック、プロジェクト構造)
任意:
- data-model.md(エンティティ定義)
- contracts/(API仕様)
- research.md(技術決定)
- quickstart.md(テストシナリオ)
4. タスク実行
tasks.md のタスクを順次実行:
実行ルール:
- フェーズ順に実行(Phase 1 → Phase 2 → ...)
- 各フェーズ内でタスクID順に実行
- [P]マーカーのあるタスクは並列実行可能
- 憲章の禁止事項を尊重(TDD必須等)
- 依存関係を確認してからタスク開始
タスク完了時:
- tasks.md のチェックボックスを更新:
- [ ]→- [x] - 変更をコミット(Conventional Commits形式)
- 次のタスクへ進む
エラー発生時:
- エラー内容を記録
- 関連するタスクにブロッキングノートを追加
- ユーザーに報告して次のアクションを確認
5. フェーズ完了チェック
各フェーズ完了時:
- フェーズ内の全タスクが完了しているか確認
- 独立テスト基準が満たされているか確認
- 次のフェーズへの移行可否を報告
6. 完了報告
- 完了したタスクID一覧
- 残タスク一覧
- 発生した問題(あれば)
- 次の推奨アクション:
- 残タスクがある場合: 続行を推奨
- 全タスク完了: PRレビューまたは追加テストを推奨
- 問題がある場合: 修正アクションを提案
ガイドライン
- タスクは独立して実行可能であるべき
- 各タスク完了後にコミット
- TDD遵守(テスト→実装→リファクタの順)
- 憲章違反を検出した場合は中断して報告
- 大きなタスクは分割を提案
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.
- 1mo ago First seen · 100 lines · 34 tokens per session scan A 25f43845d2ad
implement is a command published in the GitHub repository akiojin/unity-mcp-server (35 stars, last pushed 6d ago), licensed MIT. It adds 34 tokens to every session and 906 once invoked, about $0.0001 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.
Other commands, from other repositories
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.