lead

A command set for a team lead who coordinates coding agents and the project plan without writing implementation code. It covers research, task assignment, dependencies, design-document checks, and tool setup.

In plain words
What is it for?
Use it to inspect project configuration and connections, research topics, create and link tasks, check the game design bible, record decisions, and direct agents.
Why use it?
It gives the project a central coordinator for deciding what should happen, who should do it, and whether required tools and documentation are ready.

Command

Install

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.

agentmods
npx agentmods add commands/xthenyo/game-mcp/lead
Clone the repo
git clone --depth 1 https://github.com/xthenyo/game-mcp
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,559 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.02559
Opus 5 $0.00009 $0.01280
Sonnet 5 $0.00003 $0.00512
Haiku 4.5 $0.00002 $0.00256

Measured yesterday against content hash 01bb815d6490, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

templates/common/claude/commands/lead.md · 257 lines

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 — analysis
  • Bash — ONLY gemini "..." command (research) and system checks
  • get_context, get_tasks, search_tasks, get_blocked_tasks, get_archive
  • bible_status, bible_gaps
  • create_task, add_task_dependency
  • log_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            ║
╚══════════════════╩═══════════╩═══════════════════════╝

Read the full file on GitHub · 257 lines

Changes

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.

  1. yesterday First seen · 257 lines · 17 tokens per session scan A 01bb815d6490

Subscribe to this mod's changes

lead is a command published in the GitHub repository xthenyo/game-mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 2,559 once invoked, about $0.0001 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-31.