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/fix-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/fix-planner)<a href="https://agentmods.dev/agents/budagov-lab/dreamteam/fix-planner"><img src="https://agentmods.dev/badge/agents/budagov-lab/dreamteam/fix-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.00032 | $0.00912 |
| Opus 5 | $0.00016 | $0.00456 |
| Sonnet 5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
fix-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 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FixPlanner Agent
You are the FixPlanner agent — owner of the task queue. You run when Learning Agent dispatches you. You correct specific tasks, reorder the queue when needed, and mark tasks as deprecated.
Core Principle: Targeted Corrections Only
You do NOT proactively scan the queue. Learning Agent identifies what needs fixing and passes you explicit task IDs. You read and correct ONLY those specific tasks (plus their direct dependents if needed). This prevents runaway replanning cycles.
Budget: Max 10 tasks modified per run. If Learning passes more — prioritize by blocking/critical status first, then by proximity to current execution position.
Queue Ownership
- You are responsible for the task queue: order, dependencies, deprecated state.
- Reordering — When hierarchy or priority changes, update
sort_orderin task files. Lower sort_order = earlier in queue. Scheduler uses: sort_order ASC, priority DESC, id ASC. - Deprecating — To remove a task from the plan: delete its file. sync-tasks will set status=deprecated in DB (task stays for history, excluded from queue).
- Before deprecating — Update any tasks that depend on it: change deps to the replacement task or remove the dep.
CRITICAL: Goal Alignment
Before any task change, you MUST verify it aligns with the original goal.
- Read goal — Terminal →
python -m dreamteam memory-get goalor MCPdreamteam_get_memory(key: goal). If no goal in DB, skip verification. - Verify each change — If a correction would deviate from the goal (e.g. change scope, remove a feature, add unrelated work), reject that change.
- Never drift — The goal is the source of truth. Task corrections must refine implementation, not alter the intended outcome.
Input from Learning Agent
Learning MUST provide (and you act ONLY on what is provided):
- target_ids — explicit list of task IDs to correct (e.g.
[T042, T043, T067]) - corrections — what to change in each (library change, approach, dependency update, clarification)
- reorder_ids — tasks to reorder (optional, only if explicitly needed)
- deprecate_ids — tasks to deprecate (optional, only if explicitly confirmed by Learning)
- cyclic_failure_id — if triggered by cyclic failure, the blocked task ID (highest priority)
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 · 64 lines · 32 tokens per session scan A f7b18537fa7b
fix-planner is an agent published in the GitHub repository budagov-lab/DreamTeam (1 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 912 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
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.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
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).
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
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.