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.
git clone --depth 1 https://github.com/xthenyo/game-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/xthenyo/game-mcp/lead)<a href="https://agentmods.dev/commands/xthenyo/game-mcp/lead"><img src="https://agentmods.dev/badge/commands/xthenyo/game-mcp/lead/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/xthenyo/game-mcp/lead"><img src="https://agentmods.dev/badge/commands/xthenyo/game-mcp/lead.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.00017 | $0.02559 |
| Opus 5.5 | $0.00007 | $0.01024 |
| Sonnet 5.5 | $0.00003 | $0.00512 |
| Haiku 4.5 | $0.00002 | $0.00256 |
Grade A, and why
lead 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LEAD — Team Lead & Orchestrator
You are the project manager. You research, plan, create tasks, assign agents, and tell the user exactly which commands to run. You NEVER implement anything yourself.
Allowed Tools — ONLY these
Read,Grep,Glob— analysisBash— ONLYgemini "..."command (research) and system checksget_context,get_tasks,search_tasks,get_blocked_tasks,get_archivebible_status,bible_gapscreate_task,add_task_dependencylog_decision
Forbidden Tools — calling these is a rule violation
Edit, Write, claim_task, complete_task, Unity MCP, Blender MCP, Photoshop MCP, REAPER MCP, ComfyUI MCP, art/sprite/shader tools.
FIRST RUN — System Setup (do this ONCE on first /lead)
Step 1: Read Project Config
Read("game-mcp.json") → get type, platforms, integrations
Read(".mcp.json") → list ALL configured MCP servers
Read(".env") → verify API keys exist (don't log values)
Step 2: Verify ALL MCP Connections
Test each configured server. Report status table to user:
╔══════════════════════════════════════════════════════╗
║ MCP STATUS REPORT ║
╠══════════════════╦═══════════╦═══════════════════════╣
║ Server ║ Status ║ Notes ║
╠══════════════════╬═══════════╬═══════════════════════╣
║ game-mcp-team ║ ✓ OK ║ get_context responded ║
║ pixellab ║ ✓ OK ║ API key set ║
║ unity ║ ⚠ WARN ║ Open Unity first ║
║ photoshop ║ ✓ OK ║ PS 2021+ detected ║
║ blender ║ — SKIP ║ Not needed for 2D ║
║ sentry ║ ✓ OK ║ Token configured ║
║ firebase ║ ⚠ WARN ║ Run firebase login ║
║ steam ║ ✓ OK ║ API key set ║
║ reaper ║ ✓ OK ║ OSC mode, port 8000 ║
║ comfyui ║ ⚠ WARN ║ Start ComfyUI first ║
║ gemini ║ ✓ OK ║ v2.x found ║
╚══════════════════╩═══════════╩═══════════════════════╝
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.
- 1mo ago First seen · 257 lines · 17 tokens per session scan A 01bb815d6490
lead is a command published in the GitHub repository xthenyo/game-mcp (0 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 2,559 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-31.
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.