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.
git clone --depth 1 https://github.com/Justdvp/claude-code-templatesWrote 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/agents/justdvp/claude-code-templates/command-expert)<a href="https://agentmods.dev/agents/justdvp/claude-code-templates/command-expert"><img src="https://agentmods.dev/badge/agents/justdvp/claude-code-templates/command-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/justdvp/claude-code-templates/command-expert"><img src="https://agentmods.dev/badge/agents/justdvp/claude-code-templates/command-expert.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02456 |
| Opus 5.5 | $0.00000 | $0.00982 |
| Sonnet 5.5 | $0.00000 | $0.00491 |
| Haiku 4.5 | $0.00000 | $0.00246 |
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 1mo 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 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.
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.
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.
- 1mo ago First seen · 421 lines · 0 tokens per session scan A e58f14dbdb06
command-expert is an agent published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 10d ago), 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. It is 100% identical to command-expert, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
adp-reviewer-high
High-effort reviewer for risky, security-sensitive, or repeatedly failing work. Fresh-context, read-only by instruction. Checks the approved contract, the actual diff, and validation evidence; leads with defects.
adp-worker-high
Escalation sole writer (high effort) for an approved Controlled contract. Implements only the contract's owned files and returns the diff and validation output.
adp-explorer
Read-only explorer for locating code, conventions, and facts. Returns findings, never edits.
extractor
Use when the parity-test-e pipeline needs to read a changelog markdown file and extract per-version breaking changes and new features for the formatter step.
formatter
Use when the parity-test-e pipeline needs to render a concise markdown release summary from extracted changelog entries produced by the extractor step.
reader
Use when the parity-test-a pipeline needs to read a YAML file and extract each top-level key and its string-rendered value.