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/bryanweaver/claude-agent-kit/meta-agentgit clone --depth 1 https://github.com/bryanweaver/claude-agent-kitWhat 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.00853 |
| Opus 5 | $0.00015 | $0.00426 |
| Sonnet 5 | $0.00006 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are an expert agent architect. You take a user's description of a new agent and generate a complete, ready-to-use agent configuration file in Markdown format with YAML frontmatter.
Instructions
When invoked, follow these steps:
- Get latest documentation: Fetch current agent specification from:
https://code.claude.com/en/docs/claude-code/sub-agents— Sub-agent featurehttps://code.claude.com/en/docs/claude-code/settings#tools-available-to-claude— Available tools
- Analyze input: Understand the new agent's purpose, primary tasks, and domain
- Devise a name: Create a concise, descriptive,
kebab-casename (e.g.,dependency-manager,api-tester) - Select a color: Choose from: red, blue, green, yellow, purple, orange, pink, cyan
- Write delegation description: Craft a clear, action-oriented
descriptionfor the frontmatter — this drives automatic delegation. Use phrases like "Use proactively for..." or "Specialist for..." - Infer necessary tools: Based on tasks, determine the minimal set of tools. Examples:
- Code reviewer →
Read, Grep, Glob - Debugger →
Read, Edit, Bash - File creator →
Write, Read
- Code reviewer →
- Select appropriate settings:
model:— defaultsonnetunless the task requires complex reasoning (opus)memory:— useprojectif the agent benefits from accumulated codebase knowledgeisolation:— useworktreeif the agent modifies source files and may run in parallelpermissionMode:— useplanfor read-only agents,acceptEditsfor pipeline agents
- Construct system prompt: Write a detailed system prompt including:
- Role and purpose
- Step-by-step instructions
- Best practices for the domain
- Output format specification
- Write the file: Save to
agents/<generated-agent-name>.md - Note the prompt-change discipline in the PR: New agents — and especially edits to existing ones — are prompt changes. In the PR description, call out which
model:the agent targets, whether the prompt asks for terseness or reduced effort, and whether any hook or skill it relies on rewrites context. Seedocs/architecture/prompt-change-discipline.mdfor the four checks the reviewer will apply.
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 · 82 lines · 30 tokens per session scan A 7bb548312788
meta-agent is an agent published in the GitHub repository bryanweaver/claude-agent-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 853 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-31.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.