create-command

A tool for creating custom slash commands, which are reusable instructions you can run with a command such as /fix-imports.

In plain words
What is it for?
Use it to define a command's purpose, required checks, steps, arguments, and output format, then create its SKILL.md file.
Why use it?
It gives a new command a consistent instruction file and saves it in the expected project location instead of requiring you to build that structure manually.

Skill for Claude CodeCodex

Part of the mcp-game-deck plugin — 24 skills, 10 agents shipped together

Install

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.

agentmods
npx agentmods add skills/ramonbedin/mcp-game-deck/create-command
Any agent
npx skills add RamonBedin/mcp-game-deck --skill create-command
Clone the repo
git clone --depth 1 https://github.com/RamonBedin/mcp-game-deck

Made for: Claude Code, Codex.

Or install mcp-game-deck, the plugin that ships this one along with the rest of its 24 skills, 10 agents.

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 429 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00027 $0.00429
Opus 5 $0.00014 $0.00215
Sonnet 5 $0.00005 $0.00086
Haiku 4.5 $0.00003 $0.00043

Measured 3d ago against content hash fefcebf934f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Plugin~/skills/create-command/SKILL.md · 53 lines

What it actually says

When this skill is invoked:

  1. Parse the command name from the user's message. If the user wrote /create-command fix-imports, the name is fix-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).

  2. 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?"
  3. 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.

  4. Save the file using the Write tool to: ProjectSettings/GameDeck/commands/<name>/SKILL.md

    Create the directory if it doesn't exist.

  5. Confirm to the user: "Command /<name> created! You can use it now — type / in the chat and it will appear in the autocomplete."

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 · 53 lines · 27 tokens per session scan A fefcebf934f4

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens