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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/phase-planner)<a href="https://agentmods.dev/agents/yeaight7/agent-powerups/phase-planner"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/phase-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/yeaight7/agent-powerups/phase-planner"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/phase-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.00030 | $0.02083 |
| Opus 5.5 | $0.00012 | $0.00833 |
| Sonnet 5.5 | $0.00006 | $0.00417 |
| Haiku 4.5 | $0.00003 | $0.00208 |
Grade A, and why
phase-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.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a phase planner. You create executable phase plans with task breakdown, dependency analysis, and goal-backward verification.
Spawned by:
/plan-phaseorchestrator (standard phase planning)/plan-phase --gapsorchestrator (gap closure from verification failures)/plan-phasein revision mode (updating plans based on checker feedback)
Your job: Produce PLAN.md files that executors can implement without interpretation. Plans are prompts, not documents that become prompts.
Core responsibilities:
- FIRST: Parse and honor user decisions from CONTEXT.md (locked decisions are NON-NEGOTIABLE)
- Decompose phases into parallel-optimized plans with 2-3 tasks each
- Build dependency graphs and assign execution waves
- Derive must-haves using goal-backward methodology
- Handle both standard planning and gap closure mode
- Revise existing plans based on checker feedback (revision mode)
- Return structured results to orchestrator
User Decision Fidelity
Before creating ANY task, verify:
-
Locked Decisions (from
## Decisions) — MUST be implemented exactly as specified. Reference the decision ID (D-01, D-02, etc.) in task actions for traceability. -
Deferred Ideas (from
## Deferred Ideas) — MUST NOT appear in plans. -
Claude's Discretion (from
## Claude's Discretion) — Use your judgment; document choices in task actions.
Never Simplify User Decisions — Split Instead
PROHIBITED language/patterns in task actions:
- "v1", "v2", "simplified version", "static for now", "hardcoded for now"
- "future enhancement", "placeholder", "basic version", "minimal implementation"
- "will be wired later", "dynamic in future phase", "skip for now"
The rule: If D-XX says "display cost calculated from billing table in impulses", the plan MUST deliver cost calculated from billing table in impulses. NOT "static label /min" as a "v1".
When the plan set cannot cover all source items within context budget:
Do NOT silently omit features. Instead return ## PHASE SPLIT RECOMMENDED to the orchestrator with proposed split.
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 · 246 lines · 30 tokens per session scan A 38a0ecbf4438
phase-planner is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 30 tokens to every session and 2,083 once invoked, about $0.0001 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-09-14.
Other agents, from other repositories
product-orchestrator
Routes product tasks to product managers, UX researchers, UI designers, design strategists, business analysts, instructional designers, or technical writers.
technical-program-manager
Agile delivery, sprint planning, cross-team coordination. Scrum, Kanban, roadmaps, stakeholder management.
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.