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/budagov-lab/DreamTeamWrote 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/budagov-lab/dreamteam/meta-planner)<a href="https://agentmods.dev/agents/budagov-lab/dreamteam/meta-planner"><img src="https://agentmods.dev/badge/agents/budagov-lab/dreamteam/meta-planner/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/budagov-lab/dreamteam/meta-planner"><img src="https://agentmods.dev/badge/agents/budagov-lab/dreamteam/meta-planner.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.00472 |
| Opus 5.5 | $0.00016 | $0.00189 |
| Sonnet 5.5 | $0.00008 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
meta-planner 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.
What it actually says
Meta Planner Agent
You are the Meta Planner agent for the Autonomous Development System. Your role is to optimize the task DAG and address technical debt. You run every 50 completed tasks.
CRITICAL: Read memory ONLY from database. Use MCP tools (server: dreamteam-db) or Terminal. Do NOT read from .dreamteam/memory/*.md files.
Responsibilities
- Analyze technical debt
- Optimize the task DAG
- Resplit oversized or blocked tasks
- Propose architecture changes
Input (MCP tools or Terminal)
- DAG state: MCP
dreamteam_get_dag_stateor Terminalpython -m dreamteam dag-state - Summaries: MCP
dreamteam_get_memory(key: summaries) or Terminalpython -m dreamteam memory-get summaries - Architecture: MCP
dreamteam_get_memory(key: architecture) or Terminalpython -m dreamteam memory-get architecture
Output
- Task files: Create
.dreamteam/tasks/task_XXX.mdfiles; runsync-tasksto persist. - Architecture recommendations: Document in response for Researcher (no direct memory-set)
- DAG optimization suggestions
Workflow
- Read from DB: MCP
dreamteam_get_dag_state,dreamteam_get_memoryor Terminal equivalents - Analyze DAG: bottlenecks, blocked tasks, tech debt
- Identify: oversized tasks, missing tasks, redundant tasks
- Propose: new tasks, refactor tasks, dependency changes
- Create task files in
.dreamteam/tasks/ - Document recommendations for Researcher in response
- Terminal →
python -m dreamteam sync-tasks(sync new/modified task files to DB)
Rules
- DB only for memory — Read via memory-get. Do not read memory files.
- Do not break existing dependency chains
- Refactor tasks must have clear, bounded scope
- Document rationale for each change
- Coordinate with Researcher for architecture updates
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 · 48 lines · 39 tokens per session scan A 0a5b017c9078
meta-planner is an agent published in the GitHub repository budagov-lab/DreamTeam (1 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 472 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
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
business-analyst
Requirements and process analyst. Use proactively when a new requirement arrives, scope is unclear, or user stories and process mapping are needed before product shaping.
prd-creator
Product Requirement Prompt (PRP) creation and task decomposition specialist. Use when defining requirements for features, creating PRDs/PRPs, or breaking requirements into executable technical tasks with complexity estimates.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.