Borrowing it
Nothing to install: this file belongs to akiojin/unity-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/akiojin/unity-mcp-server/main/.claude/commands/speckit.analyze.mdgit 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.analyze)<a href="https://agentmods.dev/commands/akiojin/unity-mcp-server/speckit.analyze"><img src="https://agentmods.dev/badge/commands/akiojin/unity-mcp-server/speckit.analyze/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/speckit.analyze"><img src="https://agentmods.dev/badge/commands/akiojin/unity-mcp-server/speckit.analyze.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.00031 | $0.00550 |
| Opus 5.5 | $0.00012 | $0.00220 |
| Sonnet 5.5 | $0.00006 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
speckit.analyze 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 2mo 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.md・plan.md・tasks.md の間で矛盾/重複/曖昧さ/抜け漏れがないかを検出し、修正方針を提示します。
重要な制約
- 厳密に読み取り専用: ファイルを編集しない。分析レポートのみ出力する。
- 憲章優先:
docs/constitution.md（または.specify/memory/constitution.md）と矛盾する場合は最優先で指摘する。
実行手順
-
リポジトリルートから
.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasksを実行し、FEATURE_DIRを取得します（絶対パス）。 -
FEATURE_DIRから以下を読み込みます:- spec.md, plan.md, tasks.md（必須）
- 憲章（docs/constitution.md / .specify/memory/constitution.md）
-
検出観点（例）:
- 要件に対してタスクが割り当てられていない（Coverageギャップ）
- タスクがどの要件/ストーリーにも紐づいていない（Unmapped tasks）
- 同義・重複要件（Duplication）
- 曖昧語（"高速" "安全" など）の定量化不足（Ambiguity）
- 用語揺れ/データ定義の不一致（Terminology drift）
- 憲章MUST違反（Constitution conflict）
-
Markdownの分析レポートを出力します（ファイル書き込みなし）:
- 指摘ID、カテゴリ、深刻度（CRITICAL/HIGH/MEDIUM/LOW）、場所、要約、推奨対応
- 要件→タスクのカバレッジ要約
- 次の推奨アクション（CRITICALがあれば実装前に修正推奨）
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.
- 2mo ago First seen · 42 lines · 31 tokens per session scan A fb5f7af1ecb9
speckit.analyze is a command published in the GitHub repository akiojin/unity-mcp-server (35 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 550 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
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).