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/matteocervelli/llms/cc-command-creategit clone --depth 1 https://github.com/matteocervelli/llmsWhat 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.00000 | $0.01976 |
| Opus 5 | $0.00000 | $0.00988 |
| Sonnet 5 | $0.00000 | $0.00395 |
| Haiku 4.5 | $0.00000 | $0.00198 |
Grade A, and why
cc-command-create 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 today.
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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{}
description: Create a new Claude Code command using the command builder tool argument-hint: [name] [description] [--tech ] [--doc-url ] [--depth ]
Create Claude Code Command
Create a new Claude Code slash command using the interactive command builder with optional documentation integration.
Usage
/cc-command-create # Interactive wizard
/cc-command-create my-command # With name (will prompt for details)
/cc-command-create my-command "Description" # Quick create
# With documentation integration
/cc-command-create test-runner "Run pytest tests" --tech pytest
/cc-command-create api-docs "Generate API docs" --doc-url https://docs.example.com --depth 2
💡 Pro Tip: For safer command planning, activate Plan Mode (press Shift+Tab twice) before running this command. This allows you to review the command structure before creation.
What it does
- Launches interactive command builder wizard
- Guides you through command creation:
- Command name (slug format)
- Description
- Scope (global/project/local)
- Template selection
- Parameters (optional)
- Bash commands (optional)
- File references (optional)
- Thinking mode (optional)
- Optional: Fetch library documentation via Context7
- Optional: Deep-crawl documentation sites via Crawl4AI
- Generates command file with inline documentation references
- Adds to catalog for tracking
- Shows usage example
Parameters
name: Command name (slug format, follows [context-]object-action[-modifier] pattern)description: Brief description of what the command does--tech <library>: Fetch documentation for a specific library/framework via Context7--doc-url <url>: URL to documentation site to crawl--depth <n>: Crawl depth for multi-level documentation (1-3, default: 1)
Documentation Integration
Context7 Integration
Fetch up-to-date library documentation when creating commands:
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.
- today First seen · 280 lines · 0 tokens per session scan A 5278019dde5a
cc-command-create is a command published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,976 tokens. 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-09-01.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.