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.taskstoissues.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.taskstoissues)<a href="https://agentmods.dev/commands/akiojin/unity-mcp-server/speckit.taskstoissues"><img src="https://agentmods.dev/badge/commands/akiojin/unity-mcp-server/speckit.taskstoissues/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.taskstoissues"><img src="https://agentmods.dev/badge/commands/akiojin/unity-mcp-server/speckit.taskstoissues.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.00027 | $0.00311 |
| Opus 5.5 | $0.00011 | $0.00124 |
| Sonnet 5.5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
speckit.taskstoissues 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
空でない場合、続行する前にユーザー入力を考慮する必要があります。
実行手順
-
リポジトリルートから
.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasksを実行し、FEATURE_DIRを取得します（絶対パス）。 -
FEATURE_DIR/tasks.mdを読み込み、チェックボックス形式のタスクを抽出します。 -
GitリモートURLを取得します:
git config --get remote.origin.url注意: リモートが GitHub のURLでない場合は中止してください。
-
タスクごとにIssueを作成します（作成先はリモートURLのリポジトリと一致すること）:
- タイトル:
[FEATURE_ID] T### <短い要約> - 本文: tasks.md の該当タスク行、関連ファイルパス、依存関係、必要ならチェックリスト
- タイトル:
警告: リモートURLと一致しないリポジトリにIssueを作成してはいけません。
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 · 32 lines · 27 tokens per session scan A fc761cac4e8a
speckit.taskstoissues is a command published in the GitHub repository akiojin/unity-mcp-server (35 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 311 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
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.