meta-agent

A meta-agent definition for creating specialized coding agents. It describes how to define an agent's role, permissions, model choice, instructions, and verification process.

In plain words
What is it for?
Use it when a project needs a new specialist agent, such as one for a particular technology, review task, or development workflow.
Why use it?
It provides a repeatable way to create focused agents without giving them more access or responsibility than they need.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/liortesta/clawdagent/meta-agent
Clone the repo
git clone --depth 1 https://github.com/liortesta/ClawdAgent

Made for: Claude Code.

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 476 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash 75148eddbc64, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/agents/meta-agent.md · 65 lines

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

  1. Analyze the required capability — what problem does this agent solve?
  2. Determine optimal tool permissions (minimum necessary — principle of least privilege)
  3. Choose the right model:
    • opus — complex reasoning, strategic decisions, security-critical
    • sonnet — routine tasks, code generation, reviews
    • haiku — fast/cheap, simple lookups, quick scans
  4. Write a comprehensive system prompt with specific, actionable instructions
  5. Save to .claude/agents/[name].md with proper YAML frontmatter
  6. 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.

Changes

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.

  1. 3d ago First seen · 65 lines · 30 tokens per session scan A 75148eddbc64

Subscribe to this mod's changes

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.