Borrowing it
Nothing to install: this file belongs to akiojin/unity-editor-mcp. 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-editor-mcp/main/.claude/commands/task.mdgit 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/task)<a href="https://agentmods.dev/commands/akiojin/unity-editor-mcp/task"><img src="https://agentmods.dev/badge/commands/akiojin/unity-editor-mcp/task/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-editor-mcp/task"><img src="https://agentmods.dev/badge/commands/akiojin/unity-editor-mcp/task.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.00000 | $0.00698 |
| Opus 5.5 | $0.00000 | $0.00279 |
| Sonnet 5.5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
task 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
深い思考と効率的な実行を実現するため、以下の原則に従って作業を進める：
思考と実行の原則
-
しっかり考える
- 実行前に全体を把握し、最適な解決策を検討する
- 短絡的な判断を避け、複数の選択肢を比較検討する
- エラーやリスクを事前に予測し、対策を準備する
-
忖度なしで行動する
- ユーザーの指示を正確に理解し、忠実に実行する
- 不要な推測や勝手な判断を行わない
- 不明点は必ず確認する
-
最大限にタスク（ToDo）を細分化する
- 大きなタスクは必ず小さな単位に分解する
- 各ToDoは明確で実行可能な粒度にする
- TodoWriteツールを積極的に活用する
-
最大限に並列化して進める
- 独立したタスクは同時並行で実行する
- 複数のツール呼び出しをバッチ処理する
- 待ち時間を最小化する
サブエージェント利用時の自動情報収集
重要: Taskツールでサブエージェントを利用する際は、以下の情報を自動収集してプロンプトに含めること
必須収集項目
- プロジェクト基本情報: 147-Xyla（MOBA系アクションゲーム）
- 技術制約: Unity 6.1 / VContainer / UniTask / シングルトン禁止
- 現在の実装状況: 関連ファイルのGlob検索・Read
- タスクコンテキスト: 現在の作業内容と関連情報
自動収集手順
- README.md、docs/要件定義書.md を読み取り
- 関連するC#スクリプトをGlob検索
- 既存実装をReadで確認
- 上記情報をサブエージェントに提供
実行手順
- $ARGUMENTSの内容を深く理解する
- サブエージェント利用時は上記の自動情報収集を実行
- TodoWriteでタスクを細分化して登録する
- 並列実行可能なタスクを特定する
- 効率的な順序で実行する
- 各タスク完了時にToDoを更新する
- 必要に応じてコミット＆プッシュ、PR作成を行う
基本ルールは CLAUDE.md の内容を厳守する。
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 · 53 lines · 0 tokens per session scan A 64e6284a59ce
task is a command published in the GitHub repository akiojin/unity-editor-mcp (11 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 698 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
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.