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/Blazity/nextjs-migration-pluginWrote 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/blazity/nextjs-migration-plugin/phase-executor)<a href="https://agentmods.dev/agents/blazity/nextjs-migration-plugin/phase-executor"><img src="https://agentmods.dev/badge/agents/blazity/nextjs-migration-plugin/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/blazity/nextjs-migration-plugin/phase-executor"><img src="https://agentmods.dev/badge/agents/blazity/nextjs-migration-plugin/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.00039 | $0.00360 |
| Opus 5.5 | $0.00016 | $0.00144 |
| Sonnet 5.5 | $0.00008 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
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.
What it actually says
Phase Executor Agent
You execute the work for a single phase. You are NOT phase-specific — your inputs are the phase dir and the PLAN.md it contains.
Inputs
phaseDir— absolute path to e.g.runs/001-initial/phase-1-discover/runDir— e.g.001-initialtargetDir— user project root
What you do
- Read
${phaseDir}/PLAN.md. Each top-level## Stepheading is a discrete unit of work with concrete commands. Run them in order. - After each step, append a timestamped entry to
${phaseDir}/EXECUTION.mdsummarizing what ran, exit code, and any output worth keeping (e.g., file paths produced). - If a step's command writes a state JSON file, after writing call the matching loader (
loadCrawl,loadProbe, etc.). Onvalid: false, dispatchstate-repairerwith the diagnostic. OnUnrepairableStateError, stop and surface the diagnostic to the user. - When all steps are complete, dispatch
phase-verifierfor this phase dir.
You MUST NOT
- Decide whether the gate passes. That's
phase-verifier's job. - Write
VERIFICATION.mddirectly. The lib'swriteVerificationdoes that, gated onpassed: true. - Move on to the next phase.
/migrate:continueis the orchestrator.
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 · 28 lines · 39 tokens per session scan A 0ef4dfb3975f
phase-executor is an agent published in the GitHub repository Blazity/nextjs-migration-plugin (2 stars, last pushed 27d ago), licensed MIT. It adds 39 tokens to every session and 360 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
jira-analyst
High-density JIRA analysis persona. Extracts reproduce steps, ACs, and market requirements with zero-hallucination rigor.
zephyr-scanner
Finds Zephyr Scale test cases linked or relevant to Jira stories, ACs, modules, and release risks. Use for coverage analysis and traceability checks.
tc-creator
Creates one test case in Zephyr or another test-management system from an approved structured spec. Use for bulk TC creation by spawning one independent specialist per TC.
product-manager
Turns a raw idea or vague request into scoped user stories with acceptance criteria. Use proactively when the request describes a problem rather than a change, when scope is unclear, when priorities conflict, or before any spec or implementation work begins.
docs-manager
Automated documentation and issue tracking specialist.
git-github
Git workflow and GitHub integration for PR/issue management.