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 agents/pmdevsolutions/aurelius/command-expertgit clone --depth 1 https://github.com/PMDevSolutions/AureliusWrote 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/pmdevsolutions/aurelius/command-expert)<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/command-expert"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/command-expert.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.00019 | $0.02315 |
| Opus 5 | $0.00010 | $0.01157 |
| Sonnet 5 | $0.00004 | $0.00463 |
| Haiku 4.5 | $0.00002 | $0.00231 |
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 yesterday.
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 — 423 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
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.
- yesterday First seen · 423 lines · 19 tokens per session scan A 52ccdebf21c3
command-expert is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 19 tokens to every session and 2,315 once invoked, about $0.0001 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-04.
Other agents, from other repositories
design-explorer
Autonomous agent that explores design possibilities by generating multiple Stitch screens across different styles and layouts for a given concept.
design-critique
Use this agent to perform an automated UX heuristic review of Figma screens. Trigger when the user wants feedback on their design, a UX audit of screens, or a critique before presenting/submitting their work. Context: User wants feedback on their Figma wireframes user: "Can you review my wireframes and tell me what's…
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
stitch-kit
Use this agent for anything Stitch-related: ideating designs through conversation, generating UI screens from text, editing/iterating designs, generating design variants, managing Stitch Design Systems, converting designs to production code, extracting design tokens, and running the full design-to-ship pipeline.…
_orchestrator-protocol
Bu dosya FCM projesindeki tüm orkestratör agentların uyması zorunlu 8 maddelik protokolü tanımlar. Her agent (screen-builder, ds-auditor, token-syncer) görev başlangıcında ilk eylem olarak bu dosyayı Read ile yüklemek zorundadır. Her agent dosyasında bu 8 maddeden üretilmiş 10 satırlık kondense inline checklist ayrıca…
screen-builder
DS-compliant Figma ekran üretim agent'ı. Text / yüklenmiş görsel / Figma benchmark / "fikrim yok" girdilerinden ekran üretir. "ekran tasarla", "figma'da ekran oluştur", "alternatif üret", "bu görselden ilham al" ifadeleriyle tetiklenir. Claude Code sub-agent isolation avantajıyla ana conversation context'ini temiz…