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.checklistgit 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.checklist)<a href="https://agentmods.dev/commands/akiojin/unity-mcp-server/speckit.checklist"><img src="https://agentmods.dev/badge/commands/akiojin/unity-mcp-server/speckit.checklist.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.00032 | $0.00594 |
| Opus 5 | $0.00016 | $0.00297 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
speckit.checklist 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 5d 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
チェックリストの目的（重要）
チェックリストは「実装のテスト」ではなく、要件の書き方の品質テストです。
- ❌ 実装テスト: 「ボタンが正しく動くか」「APIが200を返すか」
- ✅ 要件品質: 「すべての状態（空/エラー/復旧）に要件が定義されているか」「曖昧語が定量化されているか」
ユーザー入力
$ARGUMENTS
空でない場合、続行する前にユーザー入力を考慮する必要があります。
実行手順
-
リポジトリルートから
.specify/scripts/bash/check-prerequisites.sh --jsonを実行し、FEATURE_DIRを取得します（絶対パス）。 -
ユーザーの意図を確認します（必要に応じて最大3問）:
- チェック観点（例: UX / セキュリティ / 運用 / 可観測性 / 互換性）
- 厳密さ（軽量レビュー用 / リリースゲート級）
- 想定利用者（作者 / レビュア / QA）
-
FEATURE_DIRから以下を読み込みます:- spec.md（必須）
- plan.md（あれば）
- tasks.md（あれば）
-
FEATURE_DIR/checklists/<short-name>.mdを作成します（ファイル書き込みあり）:.specify/templates/checklist-template.mdに従う- 連番（CHK001...）で項目を作る
- 8割以上の項目に spec/plan/tasks の参照（例:
[Spec §要件]）または[Gap][Ambiguity]を付ける - 禁止: 実装をテストするような項目（Verify/Test/Confirm、クリック/レンダー/実行など）
- 推奨: 「〜が仕様として定義されているか」「〜が定量化されているか」「セクション間で矛盾がないか」
-
最後にユーザーへ以下を返します:
- 作成したチェックリストのパス
- 項目数
- 反映した観点/厳密さ/利用者
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.
- 5d ago First seen · 45 lines · 32 tokens per session scan A 8bbc1848370f
speckit.checklist is a command published in the GitHub repository akiojin/unity-mcp-server (34 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 594 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.