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/lifangda/claude-plugins/agent-expertgit clone --depth 1 https://github.com/lifangda/claude-pluginsWhat 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 | $0.00209 | $0.03433 |
| Opus 5 | $0.00105 | $0.01716 |
| Sonnet 5 | $0.00042 | $0.00687 |
| Haiku 4.5 | $0.00021 | $0.00343 |
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 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.
This is a copy
97% 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 — 477 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-plugins 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.
- 2d ago First seen · 477 lines · 0 tokens per session scan A 1c4cf09bb570
agent-expert is an agent published in the GitHub repository lifangda/claude-plugins (43 stars, last pushed 10mo ago), licensed MIT. It adds 209 tokens to every session and 3,433 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to agent-expert, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.