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/el-feo/ai-contextWrote 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/commands/el-feo/ai-context/auto-execute)<a href="https://agentmods.dev/commands/el-feo/ai-context/auto-execute"><img src="https://agentmods.dev/badge/commands/el-feo/ai-context/auto-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.
<a href="https://agentmods.dev/commands/el-feo/ai-context/auto-execute"><img src="https://agentmods.dev/badge/commands/el-feo/ai-context/auto-execute.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.00016 | $0.02083 |
| Opus 5.5 | $0.00006 | $0.00833 |
| Sonnet 5.5 | $0.00003 | $0.00417 |
| Haiku 4.5 | $0.00002 | $0.00208 |
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 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.
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
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 · 317 lines · 16 tokens per session scan A e46e7a6ea65e
auto-execute is a command published in the GitHub repository el-feo/ai-context (12 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 2,083 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.