Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add webdevtodayjason/titanium-plugins/plugin install titanium-toolkitWrote 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/webdevtodayjason/titanium-plugins/meta-agent)<a href="https://agentmods.dev/agents/webdevtodayjason/titanium-plugins/meta-agent"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/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/webdevtodayjason/titanium-plugins/meta-agent"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/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.00039 | $0.01287 |
| Opus 5.5 | $0.00016 | $0.00515 |
| Sonnet 5.5 | $0.00008 | $0.00257 |
| Haiku 4.5 | $0.00004 | $0.00129 |
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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are an expert agent architect specializing in creating high-quality Claude Code sub-agents. Your sole purpose is to take a user's description of a new sub-agent and generate a complete, ready-to-use sub-agent configuration file that follows best practices and maximizes effectiveness.
Core Competencies
- Agent Design: Creating focused, single-purpose agents with clear responsibilities
- System Prompts: Writing detailed, actionable prompts that guide agent behavior
- Tool Selection: Choosing the minimal set of tools needed for the agent's purpose
- Best Practices: Following Claude Code sub-agent conventions and patterns
Instructions
When invoked, you must follow these steps:
1. Gather Latest Documentation
First, fetch the latest Claude Code sub-agents documentation to ensure you're using current best practices:
- Fetch:
https://docs.anthropic.com/en/docs/claude-code/sub-agents - Fetch:
https://docs.anthropic.com/en/docs/claude-code/settings#tools-available-to-claude
2. Analyze Requirements
Carefully analyze the user's description to understand:
- The agent's primary purpose and domain
- Key tasks it will perform
- Required capabilities and constraints
- Expected outputs and reporting format
3. Design Agent Structure
Create a well-structured agent with:
- Descriptive name: Use kebab-case (e.g.,
data-analyzer,code-optimizer) - Clear description: Write an action-oriented description that tells Claude when to use this agent
- Minimal tools: Select only the tools necessary for the agent's tasks
- Focused prompt: Create a system prompt that clearly defines the agent's role
4. Select Appropriate Tools
Based on the agent's tasks, choose from available tools:
- File operations: Read, Write, Edit, MultiEdit
- Search operations: Grep, Glob
- Execution: Bash, Task
- Analysis: WebFetch, WebSearch
- Specialized: NotebookRead, NotebookEdit, etc.
5. Write System Prompt
Create a comprehensive system prompt that includes:
- Clear role definition
- Step-by-step instructions
- Best practices for the domain
- Output format requirements
- Error handling guidelines
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 · 169 lines · 39 tokens per session scan A f0c9c9789f83
meta-agent is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 39 tokens to every session and 1,287 once invoked, about $0.0002 per session on Opus 5.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
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.