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/khaledsaeed18/dotclaude/create-commandnpx skills add KhaledSaeed18/dotclaude --skill create-commandgit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWhat 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.00058 | $0.01043 |
| Opus 5 | $0.00029 | $0.00522 |
| Sonnet 5 | $0.00012 | $0.00209 |
| Haiku 4.5 | $0.00006 | $0.00104 |
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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a slash command: a prompt the user invokes by typing /<name>. Make it do one well-scoped action, accept its arguments cleanly, and read like a tight instruction set. Then regenerate the derived files and validate.
Source layout is commands/<category>/<name>/COMMAND.md. Commands are file-layout: the folder must contain only COMMAND.md, because it installs as the single file .claude/commands/<name>.md. The /<name> the user types comes from that filename. The category is the folder; registry.json and the README catalog are generated by pnpm gen. Never hand-edit generated files.
Hard rules: never break these
- One command, one action. A command is something the user deliberately triggers (
/write-tests,/deploy). Keep it to a single, well-scoped job. - File layout: only
COMMAND.md. No companion files;pnpm genrejects extras because the command installs as one file. - Gate side effects. If the command commits, pushes, deploys, deletes, or sends anything, state exactly what will happen and confirm before doing it. Consider
disable-model-invocation: trueso only the user can fire it. nameis globally unique and equals the folder name, kebab-case.- Never hand-write
registry.jsonor the README catalog. Runpnpm gen. - No AI/co-author mentions anywhere in the command or its output.
Step 1: Define the command
- The one action it performs, in a sentence.
- The arguments it takes, if any, and what each means.
- Who invokes it. User-only (set
disable-model-invocation: true) for anything with side effects or timing you want to control; both you and Claude for safe, read-only helpers.
Step 2: Scaffold it
From the repo root:
pnpm new --type command --category <category> --name <name> --description "<what it does>"
Current command category: testing. Reuse it or add a new folder if a different family is justified. The scaffolder enforces kebab-case and global name uniqueness and regenerates the registry.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 77 lines · 58 tokens per session scan A 13a5b71c29fc
create-command is a skill published in the GitHub repository KhaledSaeed18/dotclaude (4 stars, last pushed 7d ago), licensed MIT. It adds 58 tokens to every session and 1,043 once invoked, about $0.0003 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
release
Cut a new playback-mcp release — version bump, changelog, dev-to-main PR, tag, and npm publish via CI. Use when asked to plan or ship a new release/version.
pr
Open a pull request from dev into main for this repo, following the repo's checklist and template. Use when asked to open/create a PR, or as part of the release flow.
pyenv-native
Manages Python runtimes and project venvs via pyenv-native and pyenv-mcp. Use when installing Python, fixing which-python/venv issues, setting .python-version, pip env problems on Windows/Linux/macOS, or when MCP pyenv-native tools are available.
rpg
Build and query semantic code graphs using RPG-Encoder. Use BEFORE grep/cat/find for any question about code structure, behavior, relationships, impact, dependencies, or cross-file patterns.
src
use when generating a doc the user will read and share — specs, roadmaps, pr explainers, research reports, plans, strategy docs. trigger words: "glyph," "spec," "roadmap," "explainer," "report," "plan," "save as a doc.".
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.