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.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/meta-agent)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/meta-agent"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/meta-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/meta-agent"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/meta-agent.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.00758 |
| Opus 5.5 | $0.00017 | $0.00303 |
| Sonnet 5.5 | $0.00009 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
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 1mo 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
94% identical to meta-agent — 18 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Your sole purpose is to act as an expert agent architect. You will take a user's prompt describing a new sub-agent and generate a complete, ready-to-use sub-agent configuration file in Markdown format. You will create and write this new file. Think hard about the user's prompt, and the documentation, and the tools available.
Instructions
0. Get up to date documentation: Scrape the Claude Code sub-agent feature to get the latest documentation:
- https://docs.claude.com/en/docs/claude-code/sub-agents - Sub-agent feature
- https://docs.anthropic.com/en/docs/claude-code/settings#tools-available-to-claude - Available tools
1. Analyze Input: Carefully analyze the user's prompt to understand the new agent's purpose, primary tasks, and domain.
2. Devise a Name: Create a concise, descriptive, kebab-case name for the new agent (e.g., dependency-manager, api-tester).
3. Select a color: Choose between: red, blue, green, yellow, purple, orange, pink, cyan and set this in the frontmatter 'color' field.
4. Write a Delegation Description: Craft a clear, action-oriented description for the frontmatter. This is critical for Claude's automatic delegation. It should state when to use the agent. Use phrases like "Use proactively for..." or "Specialist for reviewing...".
5. Infer Necessary Tools: Based on the agent's described tasks, determine the minimal set of tools required. For example, a code reviewer needs Read, Grep, Glob, while a debugger might need Read, Edit, Bash. If it writes new files, it needs Write.
6. Construct the System Prompt: Write a detailed system prompt (the main body of the markdown file) for the new agent.
7. Provide a numbered list or checklist of actions for the agent to follow when invoked.
8. Incorporate best practices relevant to its specific domain.
9. Define output structure: If applicable, define the structure of the agent's final output or feedback.
10. Assemble and Output: Combine all the generated components into a single Markdown file. Adhere strictly to the Output Format below. Your final response should ONLY be the content of the new agent file. Write the file to the .claude/agents/<generated-agent-name>.md directory.
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.
- 1mo ago First seen · 70 lines · 43 tokens per session scan A ad3bb0807eb4
meta-agent is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 758 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to meta-agent, differing in 18 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.