Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add tsmztech/claude-code-plugins/plugin install claude-craftWrote 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/tsmztech/claude-code-plugins/create-command)<a href="https://agentmods.dev/skills/tsmztech/claude-code-plugins/create-command"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/create-command/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/tsmztech/claude-code-plugins/create-command"><img src="https://agentmods.dev/badge/skills/tsmztech/claude-code-plugins/create-command.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.00044 | $0.00346 |
| Opus 5.5 | $0.00018 | $0.00138 |
| Sonnet 5.5 | $0.00009 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00035 |
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 2mo 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
Create a Claude Code Slash Command
Read first: ${CLAUDE_PLUGIN_ROOT}/docs/skills.md — commands use the same frontmatter and content patterns as skills. The key difference is file placement: commands are single .md files in .claude/commands/, not directories with SKILL.md. See the note at the top about how "Custom slash commands have been merged into skills."
Determine target location
Check if the user passed a path as $ARGUMENTS.
- Path given → create at
<path>/.claude/commands/<command-name>.md personal→ create at~/.claude/commands/<command-name>.md- Nothing → ask where. Explain project vs personal scope (see "Where skills live" in the doc — same scoping rules apply to commands)
Gather requirements
Ask the user what the command should do. Use the doc to determine frontmatter fields and content patterns — they work identically to skills.
If the user needs supporting files or auto-invocation by Claude, suggest using create-skill instead, since commands don't support those features.
Create the command
Follow the conventions from the doc for file format and naming. Check if the target already exists before writing — never overwrite without asking.
After creating, tell the user how to test it.
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.
- 2mo ago First seen · 30 lines · 44 tokens per session scan A 82c8506b7b5b
create-command is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 44 tokens to every session and 346 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…