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 agentmods add skills/grutino/mtg-forja/skillnpx skills add grutino/mtg-forja --skill skillgit clone --depth 1 https://github.com/grutino/mtg-forjaWrote 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/grutino/mtg-forja/skill)<a href="https://agentmods.dev/skills/grutino/mtg-forja/skill"><img src="https://agentmods.dev/badge/skills/grutino/mtg-forja/skill.svg" alt="Measured on agentmods" 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.00136 | $0.02621 |
| Opus 5 | $0.00068 | $0.01311 |
| Sonnet 5 | $0.00027 | $0.00524 |
| Haiku 4.5 | $0.00014 | $0.00262 |
Grade A, and why
mtg-forja 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 5d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MTG Forja
Cómo analizar un mazo de Magic sin inventarse nada.
La regla que lo gobierna todo
Nunca afirmes lo que hace una carta desde la memoria. El texto de oráculo cambia
con las erratas, las cartas se parecen entre sí y la confianza no correlaciona con
el acierto. Antes de escribir una sola frase sobre una interacción, resuelve el mazo
con resolver_mazo o detectar_sinergias y lee el oráculo que devuelven.
Esto no es una precaución teórica. Errores reales cometidos por no hacerlo:
- Afirmar que una carta baraja la biblioteca cuando en realidad manda cartas al fondo. El efecto sobre el plan de victoria era el contrario del descrito.
- Dar por hecho que una tierra entraba girada bajo condición, cuando era indestructible y siempre entraba girada. Se perdió la mitad de un motor del mazo.
- Clasificar un planeswalker como artefacto porque el mazo iba de artefactos.
Si no tienes las herramientas del servidor disponibles, búscalo en la web o dilo claramente. Escribir de memoria y sonar seguro es el peor de los resultados.
Lo que el motor NO puede ver
Esto es lo primero que hay que entender, porque determina todo lo demás.
El motor de patrones solo encuentra lo que alguien escribió antes. El léxico de recursos añade lo que se deduce de flujos («A llena el cementerio, B lo aprovecha»), que es real pero superficial. Ninguno de los dos puede razonar sobre las reglas del juego, y ahí es donde está el análisis que merece la pena:
| Lo que hay que ver | Por qué ningún motor lo ve |
|---|---|
| «Apaga los artefactos del rival, pero no los tuyos» | requiere entender la asimetría de un efecto |
| «El barrido no alcanza a tus planeswalkers» | requiere inferir qué queda fuera del efecto |
| «Esa tierra solo es criatura cuando la activas, así que sobrevive» | requiere razonar sobre estados temporales |
| «Barajar descoloca la carta que habías puesto arriba» | requiere modelar posición en la biblioteca |
Eso lo pones tú, leyendo el oráculo. Si te limitas a redactar las candidatas del motor, el análisis será correcto y vacío.
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.
- 5d ago First seen · 175 lines · 0 tokens per session scan A f01f9c7a0166
mtg-forja is a skill published in the GitHub repository grutino/mtg-forja (0 stars, last pushed 9d ago), licensed MIT. It adds 136 tokens to every session and 2,621 once invoked, about $0.0007 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
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…
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.