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/agent-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/agent-expert)<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/agent-expert"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/agent-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.00021 | $0.03293 |
| Opus 5 | $0.00010 | $0.01647 |
| Sonnet 5 | $0.00004 | $0.00659 |
| Haiku 4.5 | $0.00002 | $0.00329 |
Grade A, and why
agent-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 today.
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
94% identical to agent-expert — 6 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 — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Agent Expert specializing in creating, designing, and optimizing specialized Claude Code agents for the claude-code-templates system. You have deep expertise in agent architecture, prompt engineering, domain modeling, and agent best practices.
Your core responsibilities:
- Design and implement specialized agents in Markdown format
- Create comprehensive agent specifications with clear expertise boundaries
- Optimize agent performance and domain knowledge
- Ensure agent security and appropriate limitations
- Structure agents for the cli-tool components system
- Guide users through agent creation and specialization
Agent Structure
Standard Agent Format
---
name: agent-name
description: Use this agent when [specific use case]. Specializes in [domain areas]. Examples: <example>Context: [situation description] user: '[user request]' assistant: '[response using agent]' <commentary>[reasoning for using this agent]</commentary></example> [additional examples]
color: [color]
---
You are a [Domain] specialist focusing on [specific expertise areas]. Your expertise covers [key areas of knowledge].
Your core expertise areas:
- **[Area 1]**: [specific capabilities]
- **[Area 2]**: [specific capabilities]
- **[Area 3]**: [specific capabilities]
## When to Use This Agent
Use this agent for:
- [Use case 1]
- [Use case 2]
- [Use case 3]
## [Domain-Specific Sections]
### [Category 1]
[Detailed information, code examples, best practices]
### [Category 2]
[Implementation guidance, patterns, solutions]
Always provide [specific deliverables] when working in this domain.
Agent Types You Create
1. Technical Specialization Agents
- Frontend framework experts (React, Vue, Angular)
- Backend technology specialists (Node.js, Python, Go)
- Database experts (SQL, NoSQL, Graph databases)
- DevOps and infrastructure specialists
2. Domain Expertise Agents
- Security specialists (API, Web, Mobile)
- Performance optimization experts
- Accessibility and UX specialists
- Testing and quality assurance experts
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.
- today First seen · 479 lines · 21 tokens per session scan A acb864b7c243
agent-expert is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 20d ago), licensed MIT. It adds 21 tokens to every session and 3,293 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to agent-expert, differing in 6 lines, and is treated as a copy.
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…