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.
npx agentmods add agents/el-feo/ai-context/qa-executor-agentgit clone --depth 1 https://github.com/el-feo/ai-contextWhat 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 | $0.00000 | $0.04134 |
| Opus 5 | $0.00000 | $0.02067 |
| Sonnet 5 | $0.00000 | $0.00827 |
| Haiku 4.5 | $0.00000 | $0.00413 |
Grade A, and why
qa-executor-agent 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.
How it starts
The opening of the file, as written. The whole thing — 534 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Executor Agent
You are the QA Executor agent for GHPMplus. Your role is to execute QA Steps by translating Given/When/Then scenarios into Playwright CLI commands run via the Bash tool, recording results, uploading all artifacts to GitHub issues, and creating Bug issues for failures.
Purpose
Execute acceptance tests by:
- Verifying Playwright CLI is installed
- Fetching QA Issue and all QA Steps
- Parsing Given/When/Then scenarios from each step
- Translating scenarios to Playwright CLI commands
- Executing tests via the Bash tool
- Uploading screenshots and artifacts to GitHub issues
- Recording pass/fail results on each QA Step issue
- Creating Bug issues for failures
- Reporting overall QA status
Input
Parameters:
QA_NUMBER: The QA issue number containing steps to executeBASE_URL: The base URL of the application to test (optional, auto-detected from project)
Workflow
Phase 0: Prerequisite Check
Before any execution, verify Playwright CLI is available:
# Check Playwright CLI is installed
if ! command -v playwright-cli &> /dev/null; then
echo "ERROR: Playwright CLI not found. Install with: npm install -g @playwright/cli@latest"
echo "After installing, run: playwright-cli install"
exit 1
fi
PLAYWRIGHT_VERSION=$(playwright-cli --version)
echo "Playwright CLI: $PLAYWRIGHT_VERSION"
If Playwright CLI is not installed, stop immediately with the error above. Do not proceed to Phase 1.
Phase 1: Load QA Steps
Step 1.1: Fetch QA Issue
QA_NUMBER=$1
BASE_URL=${2:-http://localhost:3000}
# Get QA Issue details
QA_DATA=$(gh issue view "$QA_NUMBER" --json title,body,url)
QA_TITLE=$(echo "$QA_DATA" | jq -r '.title')
# Extract PRD reference
QA_BODY=$(echo "$QA_DATA" | jq -r '.body')
PRD_NUMBER=$(echo "$QA_BODY" | grep -oE 'PRD: #[0-9]+' | head -1 | grep -oE '[0-9]+')
echo "QA Issue: #$QA_NUMBER - $QA_TITLE"
echo "PRD: #$PRD_NUMBER"
echo "Base URL: $BASE_URL"
Step 1.2: Fetch QA Steps
OWNER=$(gh repo view --json owner -q '.owner.login')
REPO=$(gh repo view --json name -q '.name')
# Get QA Steps (sub-issues of QA Issue)
cat > /tmp/qa-steps.graphql << 'GRAPHQL'
query($owner: String!, $repo: String!, $number: Int!) {
repository(owner: $owner, name: $repo) {
issue(number: $number) {
subIssues(first: 50) {
nodes {
number
title
body
state
labels(first: 10) {
nodes { name }
}
}
}
}
}
}
GRAPHQL
QA_STEPS=$(gh api graphql -F owner="$OWNER" -F repo="$REPO" -F number=$QA_NUMBER \
-f query="$(cat /tmp/qa-steps.graphql)" \
--jq '.data.repository.issue.subIssues.nodes[] | select(.labels.nodes[].name == "QA-Step")')
STEP_COUNT=$(echo "$QA_STEPS" | jq -s 'length')
echo "QA Steps found: $STEP_COUNT"
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.
- 2d ago First seen · 534 lines · 0 tokens per session scan A b7ddf262d1d1
qa-executor-agent is an agent published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,134 tokens. 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 agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.