execute

execute is a command for Claude Code from simonrowland/goal-flight. It costs 22 tokens per session (4,155 once invoked), scanned A, original, MIT.

A command for running queued Goal Flight tasks with worker processes, optionally in parallel.

In plain words
What is it for?
Use it to execute planned goal chunks, request a design checkpoint before selected tasks, and run independent work in separate worktrees when parallel mode is enabled.
Why use it?
It automates dispatching the next pieces of work, but may spend money and change a working copy of the code.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions Claude Code; mentions Codex; built for gstack.

Part of the goal-flight plugin — 4 skills, 18 commands, 3 hooks shipped together

Good fit Use it to execute planned goal chunks, request a design checkpoint before selected tasks, and run independent work in separate worktrees when parallel mode is enabled.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/simonrowland/goal-flight/execute
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.

Clone the repo
git clone --depth 1 https://github.com/simonrowland/goal-flight

Made for: Claude Code.

Or install goal-flight, the plugin that ships this one along with the rest of its 4 skills, 18 commands, 3 hooks.

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 execute

README.md
[![agentmods](https://agentmods.dev/badge/commands/simonrowland/goal-flight/execute/github.svg)](https://agentmods.dev/commands/simonrowland/goal-flight/execute)
Your own site
<a href="https://agentmods.dev/commands/simonrowland/goal-flight/execute"><img src="https://agentmods.dev/badge/commands/simonrowland/goal-flight/execute/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.

agentmods 80×15 button for execute

Your own site · 80×15
<a href="https://agentmods.dev/commands/simonrowland/goal-flight/execute"><img src="https://agentmods.dev/badge/commands/simonrowland/goal-flight/execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,155 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00022 $0.04155
Opus 5.5 $0.00009 $0.01662
Sonnet 5.5 $0.00004 $0.00831
Haiku 4.5 $0.00002 $0.00415

Measured 27d ago against content hash 757aa6e1988e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

execute 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 27d 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.

commands/execute.md · 346 lines

How it starts

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

execute [--parallel ]

Execute the next goal-queue chunks with procedural workers and compact status.

⚠ DISPATCHES WORKERS. Spawns worker processes, leases capacity (costs money), and may mutate a worktree. See "Command danger classification" in SKILL.md. The standing com.goalflight.drain daemon (every ~60s, always-on) launches anything queued — draining is automatic, not a manual step.

Read:

  • protocols/session-preflight.md
  • protocols/dispatch-routing.md
  • protocols/worker-markers.md
  • protocols/worker-context-package.md
  • protocols/scout.md
  • protocols/worker-contract.md
  • protocols/state-handoff.md
  • protocols/user-status-cadence.md
  • protocols/chunk-review.md
  • protocols/milestone-review.md
  • protocols/worktrees-parallel.md only for --parallel

Two things that decide whether a dispatch is worth its tokens

Ask for a plan before the build on CP/H-class chunks — by tagging the brief. Tag it [design-checkpoint]. The worker's first deliverable is then the design — interfaces, invariants, acceptance checks, intended test names — written to the lane's research directory, followed by !USER-NEED: design ready for approval at <path>; session <resume-id>; log <path>, and it stops. Resume that session with your corrections; do not re-dispatch — re-dispatching re-pays the orientation the checkpoint exists to save. A wrong design then costs one steer instead of a whole build plus a rewrite.

This is opt-in per brief, and deliberately so. It is NOT on by default and must not be: !USER-NEED: ends the run, so a worker that checkpoints on its own initiative during an unattended execute stalls the queue until a human appears — and because the background wait correctly wakes you on that terminal, the stall looks like normal progress. Only the codex goal-mode template carries the rule today; the dispatch-wrapper path does not, so tag the brief rather than assuming the worker was told.

Collect approvals in a batch, not one at a time. A claimed controller keeps its ownership listener armed and does not enumerate dispatch ids; after each wake, use owned status to collect compatible terminal checkpoints. For an unclaimed scripted fixed-set join only, --wait takes several ids and returns when all are terminal, and a design checkpoint is terminal:

Read the full file on GitHub · 346 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. 27d ago Changed · +2 lines 757aa6e1988e
  2. 29d ago Changed · -5 lines 9c09f753cb10
  3. 1mo ago Changed · +13 tokens per session 358a58dec4b5
  4. 1mo ago Changed · +3 lines f262c2205662
  5. 1mo ago First seen · 346 lines · 9 tokens per session scan A c3578ad7d236

Subscribe to this mod's changes

execute is a command published in the GitHub repository simonrowland/goal-flight (20 stars, last pushed 22d ago), licensed MIT. It adds 22 tokens to every session and 4,155 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-08-30.