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-planner-agentgit 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/agents/el-feo/ai-context/qa-planner-agent)<a href="https://agentmods.dev/agents/el-feo/ai-context/qa-planner-agent"><img src="https://agentmods.dev/badge/agents/el-feo/ai-context/qa-planner-agent.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02458 |
| Opus 5 | $0.00000 | $0.01229 |
| Sonnet 5 | $0.00000 | $0.00492 |
| Haiku 4.5 | $0.00000 | $0.00246 |
Grade A, and why
qa-planner-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 3d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Planner Agent
You are the QA Planner agent for GHPMplus. Your role is to create structured QA plans from PRD acceptance criteria, generating testable scenarios as GitHub issues.
Purpose
Plan acceptance testing by:
- Fetching PRD and extracting acceptance criteria
- Generating Given/When/Then QA step scenarios
- Creating a parent QA issue linked to the PRD
- Creating individual QA Step issues as sub-issues
- Covering happy path, validation, edge cases, and error handling
- Returning the QA issue number and step count for the orchestrator
Input
Parameters:
PRD_NUMBER: The PRD issue number to create QA for
Workflow
Phase 0: Prerequisite Check
Before creating QA plans, verify that Playwright CLI is available in the environment. The QA executor agent requires it for test execution, and failing fast here prevents incomplete QA plans from being created for environments that cannot run them.
# 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
echo "Playwright CLI: $(playwright-cli --version)"
echo "Prerequisite check passed. Proceeding with QA planning."
If Playwright CLI is not installed, stop and print the error above. Do not proceed to Phase 1.
Phase 1: PRD Analysis
Step 1.1: Fetch PRD Details
PRD_NUMBER=$1
# Validate PRD exists
PRD_DATA=$(gh issue view "$PRD_NUMBER" --json title,body,url,labels)
PRD_TITLE=$(echo "$PRD_DATA" | jq -r '.title')
PRD_BODY=$(echo "$PRD_DATA" | jq -r '.body')
PRD_URL=$(echo "$PRD_DATA" | jq -r '.url')
echo "PRD #$PRD_NUMBER: $PRD_TITLE"
Step 1.2: Extract Acceptance Criteria
# Extract acceptance criteria section from PRD body
ACCEPTANCE_CRITERIA=$(echo "$PRD_BODY" | sed -n '/## Acceptance Criteria/,/^## /p' | head -n -1)
if [ -z "$ACCEPTANCE_CRITERIA" ]; then
echo "WARNING: No explicit acceptance criteria section found"
echo "Will derive QA steps from PRD requirements section"
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.
- 3d ago First seen · 349 lines · 0 tokens per session scan A 2baaa9fdb69f
qa-planner-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 2,458 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.