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/tsmztech/claude-code-plugins/create-commandnpx skills add tsmztech/claude-code-plugins --skill create-commandgit clone --depth 1 https://github.com/tsmztech/claude-code-pluginsWhat 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.00044 | $0.00346 |
| Opus 5 | $0.00022 | $0.00173 |
| Sonnet 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 yesterday.
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.
- yesterday 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 6mo ago), licensed MIT. It adds 44 tokens to every session and 346 once invoked, about $0.0002 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…