mtg-mcp-server: Skill for Claude Code

.agents/skills/superpowers/dispatching-parallel-agents/SKILL.md

dispatching-parallel-agents is a skill for Claude Code, Codex from j4th/mtg-mcp-server. It costs 26 tokens per session (1,363 once invoked), scanned A, a copy of dispatching-parallel-agents, MIT.

A workflow for giving separate, independent coding problems to separate agents so they can work at the same time. Each agent receives only the information it needs.

In plain words
What is it for?
Use it to investigate unrelated test failures, bugs, or subsystem problems in parallel.
Why use it?
It avoids spending time investigating unrelated failures one after another and keeps each investigation focused.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

This is j4th/mtg-mcp-server's own configuration. It tells Claude Code and Codex how to work on mtg-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mtg-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to j4th/mtg-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.

Copy the file
curl -O https://raw.githubusercontent.com/j4th/mtg-mcp-server/main/.agents/skills/superpowers/dispatching-parallel-agents/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/j4th/mtg-mcp-server

Made for: Claude Code, Codex.

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

agentmods badge for dispatching-parallel-agents

README.md
[![agentmods](https://agentmods.dev/badge/skills/j4th/mtg-mcp-server/dispatching-parallel-agents/github.svg)](https://agentmods.dev/skills/j4th/mtg-mcp-server/dispatching-parallel-agents)
Your own site
<a href="https://agentmods.dev/skills/j4th/mtg-mcp-server/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/j4th/mtg-mcp-server/dispatching-parallel-agents/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.

agentmods 80×15 button for dispatching-parallel-agents

Your own site · 80×15
<a href="https://agentmods.dev/skills/j4th/mtg-mcp-server/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/j4th/mtg-mcp-server/dispatching-parallel-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,363 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00026 $0.01363
Opus 5.5 $0.00010 $0.00545
Sonnet 5.5 $0.00005 $0.00273
Haiku 4.5 $0.00003 $0.00136

Measured 3d ago against content hash 1968923066f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dispatching-parallel-agents 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 3d 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.

Origin

This is a copy

100% identical to dispatching-parallel-agents — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/superpowers/dispatching-parallel-agents/SKILL.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dispatching Parallel Agents

Overview

You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.

When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel.

Core principle: Dispatch one agent per independent problem domain. Let them work concurrently.

When to Use

digraph when_to_use {
    "Multiple failures?" [shape=diamond];
    "Are they independent?" [shape=diamond];
    "Single agent investigates all" [shape=box];
    "One agent per problem domain" [shape=box];
    "Can they work in parallel?" [shape=diamond];
    "Sequential agents" [shape=box];
    "Parallel dispatch" [shape=box];

    "Multiple failures?" -> "Are they independent?" [label="yes"];
    "Are they independent?" -> "Single agent investigates all" [label="no - related"];
    "Are they independent?" -> "Can they work in parallel?" [label="yes"];
    "Can they work in parallel?" -> "Parallel dispatch" [label="yes"];
    "Can they work in parallel?" -> "Sequential agents" [label="no - shared state"];
}

Use when:

  • 3+ test files failing with different root causes
  • Multiple subsystems broken independently
  • Each problem can be understood without context from others
  • No shared state between investigations

Don't use when:

  • Failures are related (fix one might fix others)
  • Need to understand full system state
  • Agents would interfere with each other

The Pattern

1. Identify Independent Domains

Group failures by what's broken:

  • File A tests: Tool approval flow
  • File B tests: Batch completion behavior
  • File C tests: Abort functionality

Each domain is independent - fixing tool approval doesn't affect abort tests.

Read the full file on GitHub · 168 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. 3d ago First seen · 168 lines · 26 tokens per session scan A 1968923066f3

Subscribe to this mod's changes

dispatching-parallel-agents is a skill published in the GitHub repository j4th/mtg-mcp-server (20 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 1,363 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to dispatching-parallel-agents, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

typescript-craftsmanship

Professional TypeScript + React + Next.js coding standards enforcer. Use this skill whenever writing, reviewing, or refactoring TypeScript code in any project — whether it's a new feature, a bug fix, a refactoring pass, or a code review. Trigger on: any TypeScript or TSX file creation/editing, "clean up this code"…

KaelSensei/MagicAIBuilder · 218 tokens

mtg-commander-analysis

Expert Magic: The Gathering Commander (EDH) deck analysis, optimization, and building assistant. Use this skill whenever the user asks about Commander decks, EDH optimization, power level assessment, bracket placement, mana base construction, card cuts/additions, deck building, commander selection, synergy analysis…

KaelSensei/MagicAIBuilder · 208 tokens

clean-architecture

Clean / Hexagonal Architecture adapted to this Next.js 15 App Router + Prisma + React 19 project. Use when designing a new feature, adding a module, debating where code should live, reviewing a PR that crosses layers, or when the domain logic starts leaking into UI / routes.

KaelSensei/MagicAIBuilder · 62 tokens

web-performance

PageSpeed and Core Web Vitals checklist for web projects. Use when building UI, shipping a page, reviewing front-end code, or running /audit-code or /beautify on a web target.

KaelSensei/MagicAIBuilder · 43 tokens

clean-code

Clean Code principles applied to this TypeScript / Next.js / React project, with a strong emphasis on eliminating duplication (DRY). Use before writing new code, during refactors, after Sonar flags duplicatedlines, or when reviewing a PR that adds similar-looking code to existing modules.

KaelSensei/MagicAIBuilder · 60 tokens

mtg-rules

Magic: The Gathering comprehensive rules reference and rules engine. Use this skill whenever the user asks about MTG rules, card interactions, game mechanics, timing, priority, layers, state-based actions, combat, stack resolution, or any rules question about Magic: The Gathering. Also trigger on: 'how does X work in…

KaelSensei/MagicAIBuilder · 162 tokens