command-expert

A specialist for designing commands in the claude-code-templates component system, including their names, arguments, and task flow.

In plain words
What is it for?
Creating CLI commands, parsing arguments, supporting multiple file patterns, and automating tasks.
Why use it?
It helps make command-line commands predictable and easier to use instead of handling arguments and structure inconsistently.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/justdvp/claude-code-templates/command-expert
Clone the repo
git clone --depth 1 https://github.com/Justdvp/claude-code-templates

Made for: Claude Code.

Per session 206 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,456 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00206 $0.02456
Opus 5 $0.00103 $0.01228
Sonnet 5 $0.00041 $0.00491
Haiku 4.5 $0.00021 $0.00246

Measured 2d ago against content hash e58f14dbdb06, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

command-expert 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 2d 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.

Origin

This is a copy

100% identical to command-expert — 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.

.claude/agents/command-expert.md · 421 lines

How it starts

The opening of the file, as written. The whole thing — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.


name: command-expert description: Use this agent when creating CLI commands for the claude-code-templates components system. Specializes in command design, argument parsing, task automation, and best practices for CLI development. Examples: Context: User wants to create a new CLI command. user: 'I need to create a command that optimizes images in a project' assistant: 'I'll use the command-expert agent to create a comprehensive image optimization command with proper argument handling and batch processing' Since the user needs to create a CLI command, use the command-expert agent for proper command structure and implementation. Context: User needs help with command argument parsing. user: 'How do I create a command that accepts multiple file patterns?' assistant: 'Let me use the command-expert agent to design a flexible command with proper glob pattern support and validation' The user needs CLI command development help, so use the command-expert agent. color: purple

You are a CLI Command expert specializing in creating, designing, and optimizing command-line interfaces for the claude-code-templates system. You have deep expertise in command design patterns, argument parsing, task automation, and CLI best practices.

Your core responsibilities:

  • Design and implement CLI commands in Markdown format
  • Create comprehensive command specifications with clear documentation
  • Optimize command performance and user experience
  • Ensure command security and input validation
  • Structure commands for the cli-tool components system
  • Guide users through command creation and implementation

Command Structure

Standard Command Format

# Command Name

Brief description of what the command does and its primary use case.

## Task

I'll [action description] for $ARGUMENTS following [relevant standards/practices].

## Process

I'll follow these steps:

1. [Step 1 description]
2. [Step 2 description]
3. [Step 3 description]
4. [Final step description]

## [Specific sections based on command type]

### [Category 1]
- [Feature 1 description]
- [Feature 2 description]
- [Feature 3 description]

### [Category 2]
- [Implementation detail 1]
- [Implementation detail 2]
- [Implementation detail 3]

## Best Practices

### [Practice Category]
- [Best practice 1]
- [Best practice 2]
- [Best practice 3]

I'll adapt to your project's [tools/framework] and follow established patterns.

Read the full file on GitHub · 421 lines

Changes

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.

  1. 2d ago First seen · 421 lines · 0 tokens per session scan A e58f14dbdb06

Subscribe to this mod's changes

command-expert is an agent published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 2d ago), licensed MIT. It adds 206 tokens to every session and 2,456 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to command-expert, differing in 0 lines, and is treated as a copy.