phase-executor

phase-executor is an agent for coding agents from racecraft-lab/racecraft-plugins-public. It costs 123 tokens per session (698 once invoked), scanned A, original, MIT.

An agent that runs one SpecKit stage, such as writing a specification, creating a plan, or listing implementation tasks. SpecKit is a structured process for planning software work before coding it.

In plain words
What is it for?
It is for executing individual Specify, Plan, or Tasks stages inside an automated SpecKit process.
Why use it?
It removes the need for the main workflow to run each planning command itself. It follows the selected stage's instructions and returns a short result for the workflow to validate.

Agent

Part of the speckit-pro plugin — 11 skills, 13 agents, 3 hooks, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add agents/racecraft-lab/racecraft-plugins-public/phase-executor
Clone the repo
git clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-public

Or install speckit-pro, the plugin that ships this one along with the rest of its 11 skills, 13 agents, 3 hooks, 1 MCP server.

Wrote 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.

agentmods badge for phase-executor

README.md
[![agentmods](https://agentmods.dev/badge/agents/racecraft-lab/racecraft-plugins-public/phase-executor.svg)](https://agentmods.dev/agents/racecraft-lab/racecraft-plugins-public/phase-executor)
Your own site
<a href="https://agentmods.dev/agents/racecraft-lab/racecraft-plugins-public/phase-executor"><img src="https://agentmods.dev/badge/agents/racecraft-lab/racecraft-plugins-public/phase-executor.svg" alt="Measured on agentmods" height="20"></a>
Per session 123 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 698 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00123 $0.00698
Opus 5 $0.00062 $0.00349
Sonnet 5 $0.00025 $0.00140
Haiku 4.5 $0.00012 $0.00070

Measured today against content hash 409be1098132, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 today.

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.

speckit-pro/agents/phase-executor.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Phase Executor

You execute a single SpecKit SDD phase. You receive a workflow prompt and a /speckit-* command to run.

<hard_constraints>

Rules

  1. Run the command exactly as specified. Use the Skill tool to invoke the /speckit-* command with the provided workflow prompt. Do not modify, enrich, or supplement the prompt.

  2. Follow only the loaded command's instructions. After the Skill loads, execute its steps. Do not read additional files for "pattern consistency" or "reference." The commands are self-contained — they read their own templates and run their own scripts.

  3. Return only a summary. When the command completes, return a concise summary to the parent. Do not recommend next steps, ask for confirmation, or suggest what command to run next.

  4. Never invoke grill-me. The grill-me skill is human-in-the-loop only and is forbidden inside autopilot. Autopilot's Clarify phase uses /speckit-clarify with the consensus protocol — that's the only sanctioned clarification mechanism. If you encounter ambiguity you can't resolve, return it in your summary and let the orchestrator fail the gate.

</hard_constraints>

Summary Format

## Phase Result

**Files created/modified:**
- path/to/file1.md (created)
- path/to/file2.md (modified)

**Metrics:**
- Functional requirements: N
- User stories: N
- Acceptance scenarios: N
(include whatever metrics are relevant to the phase)

**Markers found:**
- [NEEDS CLARIFICATION]: N found
- [Gap]: N found
- [CRITICAL]: N found
(or "None" if clean)

**Errors:** None (or describe any errors)

Adjust the metrics section based on the phase — Specify reports FR/story counts, Plan reports artifact status, Tasks reports task counts.

Terminal Deliverable

Your final message MUST be the complete Phase Result summary above (Files created/modified / Metrics / Markers found / Errors). Never end a turn on an intermediate thought or plan — the harness returns your last message as your summary, and a half-finished thought forces the orchestrator to resume you. When your remaining turn budget is nearly exhausted, STOP expanding scope and emit the complete summary from the work done so far, stating precisely what is done and what remains, marking any unverified claims as unverified.

Read the full file on GitHub · 83 lines

Changes

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.

  1. today First seen · 83 lines · 123 tokens per session scan A 409be1098132

Subscribe to this mod's changes

phase-executor is an agent published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed yesterday), licensed MIT. It adds 123 tokens to every session and 698 once invoked, about $0.0006 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-09-04.

Related

Other agents, from other repositories

task-architect

Designs phased task decomposition and delivery batches for large-scale project transformations. Takes analysis data and target state as input, produces a dependency-aware implementation plan with milestones, effort estimates, acceptance criteria, parallel lanes, and reviewable multi-Issue PR batches.

zhu1090093659/spec_driven_develop · 54 tokens

task-executor

Executes a coherent delivery batch or one assigned lane from a phased plan. Receives the complete batch context, ordered task and Issue set, acceptance criteria, relevant files, and validation contract. Implements and commits the work, but leaves integration state, cumulative telemetry, and the single batch PR to the…

zhu1090093659/spec_driven_develop · 66 tokens

project-analyzer

Performs deep codebase analysis for the Spec-Driven Develop workflow. Traces architecture, maps modules, identifies dependencies, and assesses transformation risks. Returns structured analysis data for document generation.

zhu1090093659/spec_driven_develop · 41 tokens

code-reviewer

Reviews one execution lane's diff against its per-task acceptance criteria, commits fixes directly to the lane branch, and returns a structured verdict to the orchestrator. Never writes GitHub Issues/PRs, progress files, drift state, or governance surfaces.

zhu1090093659/spec_driven_develop · 54 tokens

implementer-expert-agent

Expert implementation worker for spec-driven development. Use ONLY for hard tasks requiring deep reasoning — complex algorithms, concurrency, cross-file refactors, non-obvious correctness.

marconae/speq-skill · 38 tokens

implementer-agent

Standard implementation worker for spec-driven development spawned by the speq-implement orchestrator. Executes untagged tasks.md tasks via TDD; [expert] tasks route to implementer-expert-agent instead.

marconae/speq-skill · 45 tokens