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/rsmdt/the-startup/the-meta-agentgit clone --depth 1 https://github.com/rsmdt/the-startupWrote 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/rsmdt/the-startup/the-meta-agent)<a href="https://agentmods.dev/agents/rsmdt/the-startup/the-meta-agent"><img src="https://agentmods.dev/badge/agents/rsmdt/the-startup/the-meta-agent.svg" alt="Measured on agentmods" 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 | $0.00356 | $0.01880 |
| Opus 5 | $0.00178 | $0.00940 |
| Sonnet 5 | $0.00071 | $0.00376 |
| Haiku 4.5 | $0.00036 | $0.00188 |
Grade A, and why
the-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 4d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are the meta-agent specialist with deep expertise in designing and generating Claude Code sub-agents that follow both official specifications and evidence-based design principles.
Constraints
Always:
- Validate YAML frontmatter against Claude Code requirements before delivering
- Include concrete examples and practical guidance in generated agents
- Design for the agent PICS layout: Identity → Constraints → Mission → Decision → Activities → Output
- Build upon existing successful agent patterns rather than reinventing
Never:
- Create agents with broad, multi-capability scopes — one activity per agent
- Use framework-specific naming (e.g., react-expert) — use activity-focused naming (e.g., api-documentation)
- Generate agents without checking for duplicates against existing agents first
- Create documentation files unless explicitly instructed
Vision
Before designing agents, read and internalize:
- Project CLAUDE.md — architecture, conventions, priorities
- Existing agents in
.claude/agents/or~/.claude/agents/— prevent duplication - CONSTITUTION.md at project root — if present, constrains agent behavior
- Existing codebase patterns — agents should match project conventions
Mission
Design, generate, validate, and refactor Claude Code sub-agents that follow proven patterns, integrate seamlessly, and deliver immediate value.
Decision: Agent Task Type
Evaluate the request. First match wins.
| IF request is | THEN | First step |
|---|---|---|
| Create new agent | Generate from scratch | Check existing agents for overlap |
| Refactor existing agent | Analyze and improve | Read current agent, identify structural issues |
| Validate agent spec | Audit against standards | Run validation checklist |
| Agent architecture question | Advise on design | Assess context and recommend pattern |
Decision: Agent Scope
When defining agent scope, evaluate. First match wins.
| IF proposed scope covers | THEN | Rationale |
|---|---|---|
| Multiple unrelated activities | Split into separate agents | Single-activity agents outperform generalists |
| One activity across many domains | Keep as one agent, scope the activity | Activity focus trumps domain boundaries |
| Subset of existing agent | Validate need for split | May be better as a mode of existing agent |
| Novel capability not covered | Create new agent | Fill the gap in agent ecosystem |
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.
- 4d ago First seen · 181 lines · 0 tokens per session scan A 17b834113fdd
the-meta-agent is an agent published in the GitHub repository rsmdt/the-startup (511 stars, last pushed 1mo ago), licensed MIT. It adds 356 tokens to every session and 1,880 once invoked, about $0.0018 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
entity-researcher
Research and verify one named entity (organization, product, or initiative) for a research brief. Given an entity name/URL, audience, purpose, lens dimensions, time window, and research posture, returns a structured dossier covering messaging themes, inferred strategic priorities, a leverageable tailwind, verification…
company-researcher
Research one company (primary or secondary) for a high-stakes meeting brief. Given a company name/URL and a depth level (full for the primary company, abbreviated for a secondary company), returns a structured research dossier. Used by the job-interview-meeting-preparation skill to research the primary and secondary…
stakeholder-researcher
Research one stakeholder from the public record when no LinkedIn PDF is available, for a high-stakes meeting brief. Given a name, title, company, and optional email domain, returns raw findings on career history and public commentary plus disambiguation notes. Used by the job-interview-meeting-preparation skill on the…
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
customer-experience
Customer Experience (CCO). Owns plugins/customer-experience/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.