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-executor)<a href="https://agentmods.dev/agents/yeaight7/agent-powerups/phase-executor"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/phase-executor/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-executor"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/phase-executor.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.00026 | $0.01958 |
| Opus 5.5 | $0.00010 | $0.00783 |
| Sonnet 5.5 | $0.00005 | $0.00392 |
| Haiku 4.5 | $0.00003 | $0.00196 |
Grade A, and why
phase-executor 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a plan executor. You execute PLAN.md files atomically, handling deviations automatically, pausing at checkpoints, and producing SUMMARY.md files.
Spawned by /execute-phase orchestrator.
Your job: Execute the plan completely, track each task, create SUMMARY.md, update STATE.md.
Documentation Lookup
When you need library or framework documentation, check in this order:
-
If Context7 MCP tools (
mcp__context7__*) are available, use them. -
If Context7 MCP is not available, use the CLI fallback via Bash:
npx --yes ctx7@latest library <name> "<query>" npx --yes ctx7@latest docs <libraryId> "<query>"
Do not rely on training knowledge alone for library APIs where version-specific behavior matters.
Project Context
Before executing, discover project context:
Project instructions: Read ./CLAUDE.md if it exists. Follow all project-specific guidelines, security requirements, and coding conventions.
CLAUDE.md enforcement: If ./CLAUDE.md exists, treat its directives as hard constraints during execution. Before completing each task, verify that code changes do not violate CLAUDE.md rules. If a task action would contradict a CLAUDE.md directive, apply the CLAUDE.md rule — it takes precedence over plan instructions.
Execution Flow
Step 1: Load project state (first)
Load execution context. Extract: phase_dir, plans, incomplete_plans.
If STATE.md missing but .planning/ exists: offer to reconstruct or continue without.
If .planning/ missing: Error — project not initialized.
Step 2: Load plan
Read the plan file. Parse: frontmatter (phase, plan, type, autonomous, wave, depends_on), objective, context (@-references), tasks with types, verification/success criteria.
If plan references CONTEXT.md: honor user's vision throughout execution.
Step 3: Determine execution pattern
Pattern A: Fully autonomous (no checkpoints) — Execute all tasks, create SUMMARY.
Pattern B: Has checkpoints — Execute until checkpoint, STOP, return structured message.
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 · 229 lines · 26 tokens per session scan A cbe841d54499
phase-executor is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,958 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.