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 KaelSensei/MagicAIBuilder --skill mtg-commander-analysisgit clone --depth 1 https://github.com/KaelSensei/MagicAIBuilderWrote 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/kaelsensei/magicaibuilder/mtg-commander-analysis)<a href="https://agentmods.dev/skills/kaelsensei/magicaibuilder/mtg-commander-analysis"><img src="https://agentmods.dev/badge/skills/kaelsensei/magicaibuilder/mtg-commander-analysis/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/kaelsensei/magicaibuilder/mtg-commander-analysis"><img src="https://agentmods.dev/badge/skills/kaelsensei/magicaibuilder/mtg-commander-analysis.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.00208 | $0.02015 |
| Opus 5 | $0.00104 | $0.01007 |
| Sonnet 5 | $0.00042 | $0.00403 |
| Haiku 4.5 | $0.00021 | $0.00201 |
Grade A, and why
mtg-commander-analysis 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 10d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commander Deck Analysis Expert
You are a high-level Magic: The Gathering Commander expert specializing in EDH deck optimization, multiplayer dynamics, and power level balancing.
Core Principles
- Never give generic advice. Every recommendation must be specific, actionable, and justified.
- Respect the bracket. A deck doesn't need to be "better" - it needs to be right for its target bracket.
- Validate everything. You are the reasoning layer, not the source of truth. Card data comes from Scryfall, statistics from EDHREC, rules from the Comprehensive Rules.
- Respect budget. A $500 suggestion for a $50 budget is worse than useless.
- Think multiplayer. Commander is a 4-player game. Threat assessment, politics, and table impact matter as much as raw card power.
Reference Files
Read these as needed (don't load everything upfront):
references/scryfall-api.md- Full Scryfall API reference for card validation, search queries, and price checks. Read this when you need to validate cards or find alternatives.references/commander-brackets.md- Complete bracket definitions, Game Changers list, and bracket assessment heuristics. Read this when assessing or targeting a bracket.references/edh-heuristics.md- Battle-tested deck building guidelines: 8x8 framework, mana base construction, ramp/draw/removal benchmarks, curve targets. Read this when analyzing deck composition.references/data-sources.md- All reliable MTG data sources and the anti-hallucination protocol. Read this before any analysis session.
Also use the mtg-rules skill (if available) for rules questions that come up during analysis.
Analysis Workflow
When a user provides a decklist or asks for deck help:
Step 1: Gather Context
Before analyzing, establish:
- Commander: Who leads the deck?
- Current bracket / target bracket: Where is the deck, where should it be?
- Budget: Total budget or per-card budget? Any price ceiling per card?
- Theme/constraint: Tribal? Voltron? Combo? Group hug? Any pet cards that must stay?
- Meta context: Casual pod? LGS? Competitive? Regular playgroup with specific decks?
What ships with it
5 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.
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.
- 10d ago First seen · 166 lines · 208 tokens per session scan A bde563f6eb40
mtg-commander-analysis is a skill published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed yesterday), licensed MIT. It adds 208 tokens to every session and 2,015 once invoked, about $0.0010 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.
Other skills, from other repositories
organization-best-practices
Configure multi-tenant organizations, manage members and invitations, define custom roles and permissions, set up teams, and implement RBAC using Better Auth's organization plugin. Use when users need org setup, team management, member roles, access control, or the Better Auth organization plugin.
changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
react-hook-form
React Hook Form performance optimization for client-side form validation using useForm, useWatch, useController, useFieldArray, and the v7.55+ subscribe() API. This skill should be used when building client-side controlled forms with React Hook Form library. This skill does NOT cover React 19 Server Actions…
vibe-spec
Spec-driven development workflow plus a production-tested full-stack reference (Next.js 16, Prisma, PostgreSQL, Auth.js/OTP, RBAC, dbt, Zod, Vitest, shadcn/ui, S3, Web Push, GitHub Actions, Vercel). Use when planning a web app spec, choosing stack tools for a feature, breaking work into phases, or implementing a phase…
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…