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/qingyu321/little-claude/create-commandgit clone --depth 1 https://github.com/qingyu321/Little-ClaudeWrote 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/commands/qingyu321/little-claude/create-command)<a href="https://agentmods.dev/commands/qingyu321/little-claude/create-command"><img src="https://agentmods.dev/badge/commands/qingyu321/little-claude/create-command.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00823 |
| Opus 5 | $0.00000 | $0.00411 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00082 |
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 3d 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.
This is a copy
100% identical to create-command — 0 lines 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Slash Command
Create a new slash command in both .cursor/commands/ (with trellis- prefix) and .claude/commands/trellis/ directories based on user requirements.
Usage
/trellis:create-command <command-name> <description>
Example:
/trellis:create-command review-pr Check PR code changes against project guidelines
Execution Steps
1. Parse Input
Extract from user input:
- Command name: Use kebab-case (e.g.,
review-pr) - Description: What the command should accomplish
2. Analyze Requirements
Determine command type based on description:
- Initialization: Read docs, establish context
- Pre-development: Read guidelines, check dependencies
- Code check: Validate code quality and guideline compliance
- Recording: Record progress, questions, structure changes
- Generation: Generate docs, code templates
3. Generate Command Content
Based on command type, generate appropriate content:
Simple command (1-3 lines):
Concise instruction describing what to do
Complex command (with steps):
# Command Title
Command description
## Steps
### 1. First Step
Specific action
### 2. Second Step
Specific action
## Output Format (if needed)
Template
4. Create Files
Create in both directories:
.cursor/commands/trellis-<command-name>.md.claude/commands/trellis/<command-name>.md
5. Confirm Creation
Output result:
[OK] Created Slash Command: /<command-name>
File paths:
- .cursor/commands/trellis-<command-name>.md
- .claude/commands/trellis/<command-name>.md
Usage:
/trellis:<command-name>
Description:
<description>
Command Content Guidelines
[OK] Good command content
- Clear and concise: Immediately understandable
- Executable: AI can follow steps directly
- Well-scoped: Clear boundaries of what to do and not do
- Has output: Specifies expected output format (if needed)
[X] Avoid
- Too vague: e.g., "optimize code"
- Too complex: Single command should not exceed 100 lines
- Duplicate functionality: Check if similar command exists first
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.
- 3d ago First seen · 155 lines · 0 tokens per session scan A c2825c7941b4
create-command is a command published in the GitHub repository qingyu321/Little-Claude (21 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 823 tokens. A static security scan graded it A with 0 findings. It is 100% identical to create-command, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
delegate-review
Run OCR in delegation mode — OCR handles file selection and rules, the host agent performs the actual review.
publish-skill
Sync a marketplace skill to the documentation site. Creates skill detail pages (EN/ZH), updates the marketplace index, and updates docs.json navigation.
update-faq
could you please update DESIGNFAQ & DXFAQ based on the changes we are trying to achieve.
star
Use the roster below to route a research-workflow request to exactly one STAR skill.
demo-command
Example slash command that wraps the demo-skill. Showcases the command kind.
discover
Search the Everruns(Dev) API catalog for available operations.