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 commands/guess/claude_code/create-commandgit clone --depth 1 https://github.com/guess/claude_codeWhat 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.00009 | $0.00263 |
| Opus 5 | $0.00005 | $0.00131 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
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.
This is a copy
100% identical to create-command — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Task: Create a New Custom Slash Command
Input
$ARGUMENTS
Process
-
Understand the user's intent
- Infer appropriate command name and description from the input
- Command name should be kebab-case
-
Create the command file
- Location:
.claude/commands/<command-name>.md - Start with minimal structure
- Only add complexity if needed
- Location:
Important Guidelines
- Keep instructions concise - Long instructions may be partially understood
- Start simple - Basic commands only need a Task section
- Avoid over-specification - Don't add allowed-tools unless necessary
- Focus on clarity - Simple, direct instructions work best
Minimal Template
---
description: [Command description]
---
## Task
[Brief, clear instruction]
Extended Template (when needed)
---
description: [Command description]
allowed-tools: [Only if specific tools needed]
---
## Context
[Dynamic context if helpful]
## Task
[Clear instructions]
### Arguments
$ARGUMENTS
Create the most appropriate command structure for the user's needs.
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 · 56 lines · 9 tokens per session scan A 9d7966352cbd
create-command is a command published in the GitHub repository guess/claude_code (96 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 263 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to create-command, differing in 1 line, and is treated as a copy.
Other commands, from other repositories
setup
Interactive setup for Elixir LSP development environment.
fix
Auto-fix linting, formatting, and common issues.
build
Build the project using the standard task runner.
test
Run the project test suite and report results.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.