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 pjt222/agent-almanac --skill build-tcg-deckgit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/build-tcg-deck)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/build-tcg-deck"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/build-tcg-deck/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/pjt222/agent-almanac/build-tcg-deck"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/build-tcg-deck.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 178 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00104 | $0.02152 |
| Opus 5 | $0.00052 | $0.01076 |
| Sonnet 5 | $0.00021 | $0.00430 |
| Haiku 4.5 | $0.00010 | $0.00215 |
Grade A, and why
build-tcg-deck 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 8d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build TCG Deck
Construct a trading card game deck from archetype selection through final optimization, following a structured process that works across Pokemon TCG, Magic: The Gathering, Flesh and Blood, and other major TCGs.
When to Use
- Building a new deck for a specific tournament format or casual play
- Adapting an existing deck to a changed meta-game
- Evaluating whether a new card or set release warrants a deck change
- Teaching someone the principles of deck construction
- Converting a deck concept into a tournament-ready list
Inputs
- Required: Card game (Pokemon TCG, MTG, FaB, etc.)
- Required: Format (Standard, Expanded, Modern, Legacy, Blitz, etc.)
- Required: Goal (competitive tournament, casual play, budget build)
- Optional: Preferred archetype or strategy (aggro, control, combo, midrange)
- Optional: Budget constraints (maximum spend, cards already owned)
- Optional: Current meta-game snapshot (top decks, expected field)
Procedure
Step 1: Define the Archetype
Choose the deck's strategic identity.
- Identify the available archetypes in the current format:
- Aggro: Win quickly through early pressure and efficient attackers
- Control: Answer threats efficiently, win in the late game with card advantage
- Combo: Assemble specific card combinations for powerful synergy or instant wins
- Midrange: Flexible strategy that shifts between aggro and control as needed
- Tempo: Gain resource advantage through efficient timing and disruption
- Select an archetype based on:
- Player preference and playstyle
- Meta-game positioning (what beats the top decks?)
- Budget constraints (combo decks often need specific expensive cards)
- Format legality (check ban lists and rotation status)
- Identify 1-2 primary win conditions:
- How does this deck win the game?
- What is the ideal game state this deck is trying to reach?
- State the archetype selection and win condition clearly
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.
- 8d ago First seen · 188 lines · 104 tokens per session scan A 1adacec874ca
build-tcg-deck is a skill published in the GitHub repository pjt222/agent-almanac (33 stars, last pushed yesterday), licensed MIT. It adds 104 tokens to every session and 2,152 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".
audit-docs
Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…