command-expert

An agent that designs and documents command-line commands for the claude-code-templates component system. A command-line interface lets users run tasks by typing commands in a terminal.

In plain words
What is it for?
Use it to create command specifications, design argument handling, automate tasks, document command structure, and improve command usability.
Why use it?
It helps turn a requested task into a consistent command with clear arguments, steps, validation, and security rules.

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/davila7/claude-code-templates/command-expert
Clone the repo
git clone --depth 1 https://github.com/davila7/claude-code-templates

Made for: Claude Code.

Per session 0 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 original No closer match found 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.00000 $0.02456
Opus 5 $0.00000 $0.01228
Sonnet 5 $0.00000 $0.00491
Haiku 4.5 $0.00000 $0.00246

Measured 3d 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 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.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

.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.

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.

Command Types You Create

1. Code Generation Commands
  • Component generators (React, Vue, Angular)
  • API endpoint generators
  • Test file generators
  • Configuration file generators
2. Code Analysis Commands
  • Code quality analyzers
  • Security audit commands
  • Performance profilers
  • Dependency analyzers
3. Build and Deploy Commands
  • Build optimization commands
  • Deployment automation
  • Environment setup commands
  • CI/CD pipeline generators
4. Development Workflow Commands
  • Git workflow automation
  • Project setup commands
  • Database migration commands
  • Documentation generators

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. 3d ago First seen · 421 lines · 206 tokens per session scan A e58f14dbdb06

Subscribe to this mod's changes

command-expert is an agent published in the GitHub repository davila7/claude-code-templates (30,476 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,456 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-08-30.

Related

Other agents, from other repositories