Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add basher83/lunar-claude/plugin install plugin-devWrote 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/basher83/lunar-claude/create-command)<a href="https://agentmods.dev/commands/basher83/lunar-claude/create-command"><img src="https://agentmods.dev/badge/commands/basher83/lunar-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.1 | $0.00005 | $0.00569 |
| Opus 5 | $0.00003 | $0.00284 |
| Sonnet 5 | $0.00001 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Slash Command
Phase 1: Skill Requirements Extraction (BLOCKING)
Read these files NOW before proceeding:
${CLAUDE_PLUGIN_ROOT}/skills/command-development/SKILL.md${CLAUDE_PLUGIN_ROOT}/skills/command-development/references/testing-strategies.md
After reading, output a Requirements Summary with these exact sections:
Frontmatter Fields
| Field | Purpose | Valid Values |
|---|---|---|
| [extract each field from skill] |
Argument Syntax Rules
- $ARGUMENTS: [when/how to use]
- Positional ($1, $2): [when/how to use]
- argument-hint: [format requirement]
File Reference Syntax
- @ syntax: [correct usage]
- Static vs dynamic: [difference]
Bash Execution Syntax
- Inline execution syntax: [exact format from skill]
- allowed-tools requirement: [pattern]
Command Location Rules
- Project commands: [path]
- Personal commands: [path]
- Plugin commands: [path]
Anti-Patterns (from "Critical: Commands are Instructions FOR Claude")
- Incorrect approach: [what to avoid]
- Correct approach: [what to do]
Do not proceed until this summary is complete with skill-specific content.
Phase 2: Command Specification
Command name: Purpose: Location: [project/personal/plugin] Arguments (if any): Tools needed (if any): File references (if any):
Phase 3: Implementation
Create the command file applying ALL requirements from Phase 1.
Phase 4: Testing Plan (from testing-strategies.md)
Generate a testing checklist for this specific command:
Level 1-2: Structural Validation
# [generate validation commands for this command]
Level 4: Argument Testing
| Test Case | Command | Expected |
|---|---|---|
| [generate test matrix for this command's arguments] |
Edge Cases
- [list 3-5 edge cases specific to this command]
Phase 5: Self-Verification
| Skill Requirement | Implemented? | Evidence |
|---|---|---|
| Instructions written FOR Claude (not TO user) | ||
| description < 60 chars | ||
| argument-hint matches actual arguments | ||
| allowed-tools if bash used | ||
| @ syntax correct for file refs | ||
| Single responsibility |
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 · 106 lines · 5 tokens per session scan A 38e7b4ee2cfe
create-command is a command published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It adds 5 tokens to every session and 569 once invoked, about $0.0000 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-09-03.
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.