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/ramonbedin/mcp-game-deck/create-commandnpx skills add RamonBedin/mcp-game-deck --skill create-commandgit clone --depth 1 https://github.com/RamonBedin/mcp-game-deckWhat 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 | $0.00027 | $0.00429 |
| Opus 5 | $0.00014 | $0.00215 |
| Sonnet 5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
create-command 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.
What it actually says
When this skill is invoked:
-
Parse the command name from the user's message. If the user wrote
/create-command fix-imports, the name isfix-imports. If no name was provided, ask for one. The name must be lowercase, kebab-case, no spaces (e.g.,my-command,check-layers,setup-scene). -
Ask the user what this command should do:
- "What should
/<name>do? Describe it in one sentence." - "What specific steps should it follow? What should it check? What output format should it produce?"
- "What should
-
Generate the SKILL.md file following this exact format:
--- name: <command-name> description: "<one-sentence description>" argument-hint: "<what arguments it expects, if any>" user-invocable: true allowed-tools: Read, Glob, Grep, Write, Edit, Bash --- When this skill is invoked: 1. <step 1> 2. <step 2> ... Output format: <describe the expected output>Base the allowed-tools on what the command needs. Read-only commands don't need Write/Edit. Use the existing skills in the package as reference for style and structure.
-
Save the file using the Write tool to:
ProjectSettings/GameDeck/commands/<name>/SKILL.mdCreate the directory if it doesn't exist.
-
Confirm to the user: "Command
/<name>created! You can use it now — type/in the chat and it will appear in the autocomplete."
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.
- 3d ago First seen · 53 lines · 27 tokens per session scan A fefcebf934f4
create-command is a skill published in the GitHub repository RamonBedin/mcp-game-deck (6 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 429 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…