execute

A command that starts an ADE build, where separate software agents generate and evaluate an application from a plan. It reads the plan, creates work items, and starts the agent team.

In plain words
What is it for?
Use it to execute an approved plan, update its progress, create feature tasks, and start the generator and evaluator agents.
Why use it?
It turns an approved development plan into tracked implementation work and evaluation instead of requiring one agent to handle the whole build alone.

Command

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 commands/alexsds/ade-workflow/execute
Clone the repo
git clone --depth 1 https://github.com/alexsds/ade-workflow
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 711 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.00012 $0.00711
Opus 5 $0.00006 $0.00356
Sonnet 5 $0.00002 $0.00142
Haiku 4.5 $0.00001 $0.00071

Measured yesterday against content hash 8617cbbf460e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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 · 66 lines

What it actually says

You are executing the ADE build workflow.

Step 1: Find the approved plan

Look in .ade/docs/plans/ for the most recent plan file. Read it and verify its status is approved or draft (if the user explicitly says to proceed).

If no plan exists, tell the user to run /ade:plan first.

Step 2: Read project settings

Read .claude/ade.local.md for commit style configuration.

Step 3: Update plan status

Update the plan's frontmatter status from draft/approved to in-progress.

Step 4: Create the team

Use the TeamCreate tool:

{
  "team_name": "ade-build",
  "description": "Generator + Evaluator building from approved plan"
}

Step 5: Create tasks from the plan

Read the plan and create a task (using TaskCreate) for each feature/deliverable. These tasks form the shared task list the team works from.

Step 6: Spawn teammates

Spawn both teammates using the Agent tool with team_name: "ade-build":

Generator — spawn with:

  • name: "generator"
  • team_name: "ade-build"
  • subagent_type: use the ade-generator agent
  • prompt: Tell it to read the plan, read ${CLAUDE_PLUGIN_ROOT}/skills/ade-generation/SKILL.md for methodology, check the task list, claim the first feature task, implement it, self-verify, commit to git, then message the evaluator via SendMessage (to: "evaluator") with: feature name, files changed, how to test. After evaluator responds, iterate if needed. When approved, mark task complete, claim next task.

Evaluator — spawn with:

  • name: "evaluator"
  • team_name: "ade-build"
  • subagent_type: use the ade-evaluator agent
  • prompt: Tell it to read ${CLAUDE_PLUGIN_ROOT}/skills/ade-evaluation/SKILL.md for methodology, then wait for messages from the generator. When a feature is submitted, load rubrics from ${CLAUDE_PLUGIN_ROOT}/rubrics/ and .ade/rubrics/, load testing tools from ${CLAUDE_PLUGIN_ROOT}/testing-tools/ and .ade/testing-tools/, test the feature, score against rubric criteria, then message the generator via SendMessage (to: "generator") with the scored report. If all criteria pass, say APPROVED. If any fail, say FAILED with specific fixes.

Step 7: Monitor progress

The team communicates via SendMessage. The workflow per feature:

  1. Generator implements feature, commits, messages evaluator
  2. Evaluator tests, scores, messages generator with pass/fail
  3. If failed: Generator iterates, re-submits
  4. If passed: Generator marks task complete, moves to next feature

When all tasks are complete, send teammates a shutdown message:

SendMessage({ to: "generator", message: { type: "shutdown_request" } })
SendMessage({ to: "evaluator", message: { type: "shutdown_request" } })

Then notify the user that the build is complete and suggest running /ade:done to archive the plan.

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. yesterday First seen · 66 lines · 12 tokens per session scan A 8617cbbf460e

Subscribe to this mod's changes

execute is a command published in the GitHub repository alexsds/ade-workflow (1 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 711 once invoked, about $0.0001 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-08-31.