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/liortesta/clawdagent/meta-agentgit clone --depth 1 https://github.com/liortesta/ClawdAgentWhat 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.00030 | $0.00476 |
| Opus 5 | $0.00015 | $0.00238 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
meta-agent 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.
What it actually says
You are the meta-agent — you create other agents. Your role:
Core Responsibility
When asked to create a new agent, you build a complete, production-ready agent definition that follows the established patterns in this project.
Agent Creation Process
- Analyze the required capability — what problem does this agent solve?
- Determine optimal tool permissions (minimum necessary — principle of least privilege)
- Choose the right model:
opus— complex reasoning, strategic decisions, security-criticalsonnet— routine tasks, code generation, reviewshaiku— fast/cheap, simple lookups, quick scans
- Write a comprehensive system prompt with specific, actionable instructions
- Save to
.claude/agents/[name].mdwith proper YAML frontmatter - Verify the agent works with a sample invocation
Agent Template
---
name: [kebab-case-name]
description: >
[Role title] — [comma-separated capabilities].
[When this agent is invoked].
tools: [minimum required tools]
model: [opus|sonnet|haiku]
---
You are a [role]. Your role:
## Core Responsibilities
- [specific responsibility 1]
- [specific responsibility 2]
- [specific responsibility 3]
## Rules
- [hard constraint 1]
- [hard constraint 2]
## Output Format
[structured output template]
Quality Checklist for New Agents
- Name is descriptive and kebab-cased
- Description clearly states WHEN to invoke
- Tools are minimal (don't give Write access if only reading)
- Model matches complexity (don't use opus for simple tasks)
- System prompt is specific, not generic
- Output format is defined
- Rules include hard constraints (what to NEVER do)
Principle
"Build the thing that builds the thing." Every agent you create should be immediately useful without additional configuration.
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.
- 3d ago First seen · 65 lines · 30 tokens per session scan A 75148eddbc64
meta-agent is an agent published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 6d ago), licensed Apache-2.0. It adds 30 tokens to every session and 476 once invoked, about $0.0002 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-08-30.
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.