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 skills add P47Phoenix/Claude-Plugins --skill mtg-commandergit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWrote 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/skills/p47phoenix/claude-plugins/mtg-commander)<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/mtg-commander"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/mtg-commander/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/skills/p47phoenix/claude-plugins/mtg-commander"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/mtg-commander.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.00092 | $0.10413 |
| Opus 5.5 | $0.00037 | $0.04165 |
| Sonnet 5.5 | $0.00018 | $0.02083 |
| Haiku 4.5 | $0.00009 | $0.01041 |
Grade A, and why
mtg-commander 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 — 1,185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MTG Commander Deck Builder
Multi-agent pipeline for building optimized, format-legal, budget-compliant Commander (EDH) decklists.
User-facing guide: see
README.mdfor install, quick start, and troubleshooting. Config authoring walkthrough atreferences/config-walkthrough.md.
Sub-Agent Dispatch Guardrail
Every pipeline step — primary agents and challenger agents alike — MUST be dispatched as a separate sub-agent via the Agent tool. This is NON-NEGOTIABLE.
NEVER inline any pipeline step. Running a pipeline step inside the orchestrator's own context instead of spawning a dedicated sub-agent is a GUARDRAIL VIOLATION. If you catch yourself thinking "I'll just run this step inline to save time," stop. That thought is the violation.
Rationale:
- Context isolation — each agent receives only its defined inputs (deck state, intake params, reference files). No bleed from prior agent reasoning.
- Adversarial independence — challengers MUST NOT share context with the primary they are reviewing. Shared context defeats the entire adversarial architecture.
- Correction loop integrity — self-correction routing depends on clean agent boundaries. Inlined steps corrupt the correction signal.
Anti-pattern (from real session 0876a59e):
"I'll run the agent roles inline to keep things moving..."
This collapsed all four agents into a single context window, destroyed adversarial independence, and produced a deck with 14 undetected color identity violations. The correction loop never fired because there were no agent boundaries to trigger it. NEVER repeat this.
All 8 dispatches (4 primary + 4 challenger) MUST be separate Agent tool invocations. No exceptions. No "just this once." No "it's a simple deck."
Configuration (.mtg-commander.yml)
At pipeline start (after intake confirmation, before the pipeline banner), check the user's working directory for .mtg-commander.yml.
If absent: Use all defaults. Output a one-line note: No .mtg-commander.yml found — using defaults. Create one to customize loop caps, price goals, and escalation.
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .mtg-commander.yml.example 1.9 KB
- ARCHITECTURE.md 11 KB
- LICENSE.txt 11 KB
- README.md 7.9 KB
- references/api-reference.md 12 KB
- references/archetype-patterns.md 16 KB
- references/banned-list.md 4.3 KB
- references/commander-rules.md 5.1 KB
- references/config-walkthrough.md 4.9 KB
- references/intake-questions.md 7.7 KB
- references/optimizer-guide.md 12 KB
- references/price-evaluator-guide.md 16 KB
- references/rules-judge-guide.md 13 KB
- references/structural-minimums.md 6.4 KB
- references/synergy-taxonomy.md 8.4 KB
- scripts/card_lookup.py 28 KB runs code
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 · 1,185 lines · 92 tokens per session scan A 6a761ce1935c
mtg-commander is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 10,413 once invoked, about $0.0004 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…