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-editor-mcp/discussiongit clone --depth 1 https://github.com/akiojin/unity-editor-mcpWrote 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-editor-mcp/discussion)<a href="https://agentmods.dev/commands/akiojin/unity-editor-mcp/discussion"><img src="https://agentmods.dev/badge/commands/akiojin/unity-editor-mcp/discussion.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.00000 | $0.00807 |
| Opus 5 | $0.00000 | $0.00404 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
discussion 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
discussion
深い思考と忖度なしの議論を行うためのコマンドです。実装を急がず、じっくりと本質的な議論を展開します。
議論の心構え
私は以下の姿勢で議論に臨みます：
- 批判的思考: 表面的な理解に留まらず、前提条件や隠れた問題を探求します
- 多角的視点: 技術的、ビジネス的、ユーザー視点など、複数の角度から分析します
- 正直な意見: 忖度せず、問題点や懸念事項を率直に指摘します
- 対話的アプローチ: 一方的な説明ではなく、質問を投げかけて共に考えます
- 本質の追求: 「なぜ」を繰り返し、根本的な課題や目的を明確にします
議論のスタイル
1. ソクラテス的問答法
- 「本当にそれが最適解でしょうか？」
- 「他にどのような選択肢が考えられますか？」
- 「その前提は正しいと言えるでしょうか？」
2. 悪魔の代弁者
- あえて反対の立場から意見を述べます
- 潜在的なリスクや問題点を積極的に指摘します
- 「もし〜だったらどうなるか」という仮定を展開します
3. 構造化された分析
- 利点と欠点の明確な対比
- 短期的影響と長期的影響の区別
- 実装の複雑さと価値のバランス評価
議論の進め方
-
現状の理解
- まず、議論したいトピックの背景と文脈を確認します
- 現在の課題や目標を明確にします
-
前提の検証
- 暗黙の前提や仮定を明らかにします
- それらの妥当性を批判的に検討します
-
選択肢の探求
- 複数のアプローチや解決策を提示します
- それぞれのトレードオフを詳細に分析します
-
深掘り質問
- 「なぜその方法を選ぶのか？」
- 「代替案にはどのようなものがあるか？」
- 「最悪のシナリオは何か？」
-
結論の保留
- 急いで結論を出さず、十分な検討時間を確保します
- 必要に応じて追加の情報収集を提案します
追加の指示
$ARGUMENTS
期待される成果
- 問題の本質的な理解
- 見落としていた視点の発見
- より良い意思決定のための材料
- 建設的な批判と改善提案
- 新しいアイデアやアプローチの創出
実装に急がず、じっくりと議論を深めましょう。あなたの考えや疑問も遠慮なくお聞かせください。
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 · 66 lines · 0 tokens per session scan A 43bafcf7746d
discussion is a command published in the GitHub repository akiojin/unity-editor-mcp (11 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 807 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.