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/speckit.plangit 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/speckit.plan)<a href="https://agentmods.dev/commands/akiojin/unity-mcp-server/speckit.plan"><img src="https://agentmods.dev/badge/commands/akiojin/unity-mcp-server/speckit.plan.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.00028 | $0.00652 |
| Opus 5 | $0.00014 | $0.00326 |
| Sonnet 5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
speckit.plan 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 4d 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
空でない場合、続行する前にユーザー入力を考慮する必要があります。
概要
これはSpec駆動開発ライフサイクルの2番目のステップです（仕様 → 計画）。
実行手順
-
リポジトリルートから
.specify/scripts/bash/setup-plan.sh --jsonを実行し、JSON出力から以下を取得します（パスはすべて絶対パス）:FEATURE_IDFEATURE_DIRFEATURE_SPECIMPL_PLAN
-
コンテキストを読み込みます:
FEATURE_SPEC（spec.md）docs/constitution.md（憲章。存在しない場合は.specify/memory/constitution.mdを参照）.specify/templates/plan-template.md（構造と必須セクションの理解。すでにIMPL_PLANにコピー済み）
-
IMPL_PLAN（plan.md）をテンプレート構造に沿って埋めます:- 技術コンテキストを具体化（不明点は
要明確化として明示） - 憲章チェックを、憲章のMUST/禁止事項に従って記述
- プロジェクト構造（ドキュメント/ソース）を実パスで確定
- ユーザー入力
$ARGUMENTSの技術選択・制約を反映（矛盾があれば指摘し、合理案を提示）
- 技術コンテキストを具体化（不明点は
-
設計アーティファクトを作成します（必要に応じて）:
FEATURE_DIR/research.md: 技術選定の根拠、代替案、決定事項（要明確化の解消）FEATURE_DIR/data-model.md: 主要エンティティと関係（要件/ストーリーに対応）FEATURE_DIR/contracts/: API/入出力契約（該当する場合）FEATURE_DIR/quickstart.md: 主要ユーザーストーリーを検証する最短の実行/確認手順
-
最後に、ユーザーへ以下を返します:
FEATURE_IDIMPL_PLANのパス- 生成したアーティファクト（存在するもの）の一覧
- 次ステップ（
/speckit.tasks）への案内
重要
- すべてのファイル操作は絶対パスで行い、パス解決の誤りを避けてください。
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.
- 4d ago First seen · 51 lines · 28 tokens per session scan A 0db70cf77796
speckit.plan is a command published in the GitHub repository akiojin/unity-mcp-server (34 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 652 once invoked, about $0.0001 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
sim
Run the EmbodiedGen simulation rendering workflow with sim-cli.
cert-check
Review the current state against certification and platform compliance expectations.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
tech-debt
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.
breakout
Toggle BREAK-IN in your terminal (free-play) — alias of /breakin.