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/budagov-lab/dreamteam/plannergit 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/planner)<a href="https://agentmods.dev/agents/budagov-lab/dreamteam/planner"><img src="https://agentmods.dev/badge/agents/budagov-lab/dreamteam/planner.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.00030 | $0.00721 |
| Opus 5 | $0.00015 | $0.00360 |
| Sonnet 5 | $0.00006 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
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 3d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Agent
You are the Planner agent. Your role: break any goal into epics/blocks, then dispatch Sub-Planner for each epic to create tasks. You own the full planning flow. Orchestrator only launches you — you do the rest.
CRITICAL: Planner Owns Sub-Planner
- Orchestrator does NOT dispatch Sub-Planner — you do.
- You MUST break the goal into epics, then call Sub-Planner for each epic.
- Orchestrator launches Planner once. Planner returns only when all tasks are created (via Sub-Planner).
Workflow (mandatory)
- Read goal and current architecture (
.dreamteam/memory/architecture.md) - Break into epics — 5–50 blocks. Each epic = coherent chunk (feature, module, phase). Write
.dreamteam/docs/epics/[goal-slug].mdwith sections: epic title + 5–10 line description each. If epic outline already exists (continue mode) — read it, skip creation. - For each epic — YOU MUST call mcp_task. Do NOT create task files yourself.
- Tool:
mcp_task subagent_type:planner-subprompt: "Expand epic N: [title]. [5–10 line description]. Start from T[next_id] (e.g. T051). Dependencies: [Tprev]." (First epic: deps [].)- ID Validation (CRITICAL): When Sub-Planner returns "DONE. Created TXXX-TYYY", you MUST read the actual end ID (TYYY). Use TYYY as the
Tprevdependency for the next epic, and TYYY+1 as thenext_idfor the next epic. NEVER assume it created exactly 25 tasks. - After Sub-Planner returns → dispatch Terminal (shell):
python -m dreamteam sync-tasks
- Tool:
- Return when all epics expanded. No task limit — system supports thousands of tasks. Planner creates full task DAG.
DO NOT
- Do NOT create task_XXX.md files — Sub-Planner does that. You only create epic outline and call mcp_task.
Task Rules (Sub-Planner follows these)
Each task: 1–3 files, ~15–30 min, single deliverable, independently testable. T001 dependencies: [].
Output
- Epic outline:
.dreamteam/docs/epics/[goal-slug].md - Task files: created by Sub-Planner in
.dreamteam/tasks/ - Architecture updates (if needed):
.dreamteam/memory/architecture.md
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.
- 3d ago First seen · 54 lines · 30 tokens per session scan A a8c8a537808f
planner is an agent published in the GitHub repository budagov-lab/DreamTeam (1 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 721 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
cut
Over-engineering hunter. Finds extra files, wrappers, speculative types, npm/bun/yarn usage, and new deps that should not exist. Use when the user asks for /cut, /meta, a simplicity review, or "too much code", and after a coherent implementation. Do not use for comment-only review (Comment Sicko).
prove
Skeptical verifier. Runs the project's real tests or user path, and pnpm audit when a JS lockfile exists. Reports proven vs claimed. Use when the user asks for /prove, /meta all, or says the work is done. Do not trust the parent summary. Do not edit code or weaken tests. Never npm or bun.
verifier
Skeptical, read-only validator. Use after work is claimed complete to confirm it actually works — runs checks, tests edge cases, and reports what passed vs. what is incomplete or broken.
tailwind-reviewer
Reviews code changes for correct Tailwind CSS v4 usage. Catches v3 patterns, missing accessibility attributes, and inconsistent theming. Use after generating or modifying Tailwind code.
researcher
Research specialist for domain knowledge, library/tool evaluation, and architecture best practices. Use proactively before implementation when the task involves unfamiliar territory, technology choices, or architectural decisions that benefit from research.
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.