qa-execute

A command that runs written quality checks in a web browser using Playwright, a browser-automation tool.

In plain words
What is it for?
Use it to run one QA step or all steps in a QA issue, save test results and screenshots to GitHub, and create bug issues when checks fail.
Why use it?
It removes the need to perform each acceptance check manually and records whether the tested behavior works.

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/qa-execute
Clone the repo
git clone --depth 1 https://github.com/el-feo/ai-context
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 12,421 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00007 $0.12421
Opus 5 $0.00003 $0.06211
Sonnet 5 $0.00001 $0.02484
Haiku 4.5 $0.00001 $0.01242

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

Security

Grade A, and why

qa-execute scanned grade A with 1 finding 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

const { execSync } = require('child_process');
plugins/ghpm/commands/qa-execute.md · 1,491 lines

How it starts

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

Resolution order if omitted:

  1. Most recent open QA issue with QA Steps: gh issue list -l QA -s open --limit 1 --json number -q '.[0].number'

<usage_examples> Execute a single QA Step:

/ghpm:qa-execute step=#42

Execute all Steps in a QA Issue:

/ghpm:qa-execute qa=#10

Auto-resolve most recent QA Issue:

/ghpm:qa-execute

</usage_examples>

Step 0: Resolve Target QA Steps

If step=#N provided (single Step execution)

STEP=$N

# Fetch Step details
STEP_DATA=$(gh issue view "$STEP" --json title,body,url,labels -q '.')
STEP_TITLE=$(echo "$STEP_DATA" | jq -r '.title')
STEP_BODY=$(echo "$STEP_DATA" | jq -r '.body')

# Verify it's a QA Step
HAS_LABEL=$(echo "$STEP_DATA" | jq -r '.labels[].name' | grep -c "QA-Step" || true)
if [ "$HAS_LABEL" -eq 0 ]; then
  echo "Warning: Issue #$STEP does not have QA-Step label. Proceeding anyway."
fi

# Extract parent QA Issue number from body
QA=$(echo "$STEP_BODY" | grep -oE 'QA: #[0-9]+' | head -1 | grep -oE '[0-9]+')

STEPS_TO_EXECUTE=("$STEP")

If qa=#N provided (all Steps in QA Issue)

QA=$N
OWNER=$(gh repo view --json owner -q '.owner.login')
REPO=$(gh repo view --json name -q '.name')

# Fetch all QA Steps linked as sub-issues of this QA Issue
cat > /tmp/ghpm-qa-subissues.graphql << 'GRAPHQL'
query($owner: String!, $repo: String!, $number: Int!) {
  repository(owner: $owner, name: $repo) {
    issue(number: $number) {
      subIssues(first: 50) {
        nodes {
          number
          title
          state
          labels(first: 10) {
            nodes { name }
          }
        }
      }
    }
  }
}
GRAPHQL

# Get open QA Steps
STEPS_TO_EXECUTE=$(gh api graphql -F owner="$OWNER" -F repo="$REPO" -F number=$QA \
  -f query="$(cat /tmp/ghpm-qa-subissues.graphql)" \
  --jq '.data.repository.issue.subIssues.nodes[] | select(.state == "OPEN") | select(.labels.nodes[].name == "QA-Step") | .number')

if [ -z "$STEPS_TO_EXECUTE" ]; then
  echo "Error: No open QA Steps found for QA Issue #$QA"
  exit 1
fi

echo "Found $(echo "$STEPS_TO_EXECUTE" | wc -l | tr -d ' ') QA Steps to execute"

Read the full file on GitHub · 1,491 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 · 1,491 lines · 7 tokens per session scan A 0d227ee3ccd2

Subscribe to this mod's changes

qa-execute is a command published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 12,421 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.