auto-execute

A command that starts an orchestrator to carry out a product requirements document (PRD) from beginning to end. A PRD is a written description of what should be built.

In plain words
What is it for?
Use it with a GitHub PRD issue to check that the issue is valid, review its summary, confirm execution, and delegate the work to the orchestrator.
Why use it?
It removes the need to manually break a GitHub issue into tasks and coordinate the work after deciding to proceed.

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/el-feo/ai-context/auto-execute
Clone the repo
git clone --depth 1 https://github.com/el-feo/ai-context
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,083 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.00016 $0.02083
Opus 5 $0.00008 $0.01042
Sonnet 5 $0.00003 $0.00417
Haiku 4.5 $0.00002 $0.00208

Measured 2d ago against content hash e46e7a6ea65e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

auto-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 2d 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.

plugins/ghpmplus/commands/auto-execute.md · 317 lines

How it starts

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

Example:

/ghpmplus:auto-execute prd=#42

<usage_examples>

Standard usage:

/ghpmplus:auto-execute prd=#42

→ Validates PRD #42 exists, shows summary, confirms with user, then triggers orchestrator

With existing Epics:

/ghpmplus:auto-execute prd=#42

→ If PRD already has Epics, orchestrator will use existing breakdown instead of creating new

</usage_examples>

<operating_rules>

  • Always validate that the PRD issue exists and has the "PRD" label before proceeding
  • Show PRD summary to user before triggering execution
  • Confirm execution with user before delegating to orchestrator (this is a significant autonomous action)
  • Do not create local artifacts - all work happens via GitHub issues and the orchestrator
  • Delegate fully to the orchestrator-agent once confirmed - do not duplicate its workflow </operating_rules>

Step 1: Parse Arguments

Extract PRD number from arguments:

# Parse prd=#N from $ARGUMENTS
PRD_NUMBER=$(echo "$ARGUMENTS" | grep -oE 'prd=#[0-9]+' | grep -oE '[0-9]+')

if [ -z "$PRD_NUMBER" ]; then
  echo "ERROR: PRD number required"
  echo "Usage: /ghpmplus:auto-execute prd=#<issue_number>"
  exit 1
fi

Step 2: Validate PRD Exists

# Verify PRD issue exists and has PRD label
PRD_DATA=$(gh issue view "$PRD_NUMBER" --json title,body,labels,state,url 2>/dev/null)

if [ -z "$PRD_DATA" ]; then
  echo "ERROR: Issue #$PRD_NUMBER not found"
  exit 1
fi

# Check for PRD label
HAS_PRD_LABEL=$(echo "$PRD_DATA" | jq -r '.labels[].name' | grep -c "^PRD$" || echo "0")

if [ "$HAS_PRD_LABEL" -eq 0 ]; then
  echo "WARNING: Issue #$PRD_NUMBER does not have 'PRD' label"
  echo "This may not be a valid PRD. Proceeding anyway..."
fi

# Check if PRD is open
STATE=$(echo "$PRD_DATA" | jq -r '.state')
if [ "$STATE" = "CLOSED" ]; then
  echo "ERROR: PRD #$PRD_NUMBER is already closed"
  exit 1
fi

Read the full file on GitHub · 317 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. 2d ago First seen · 317 lines · 16 tokens per session scan A e46e7a6ea65e

Subscribe to this mod's changes

auto-execute is a command published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 2,083 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-30.