qa

qa is an agent for Claude Code from espennilsen/pi. It costs 12 tokens per session (1,512 once invoked), scanned A, original, MIT.

A QA agent that tests a running web application as a real user and reports evidence against acceptance criteria. QA means checking whether software behaves as required; it does not modify code.

In plain words
What is it for?
Use it to load an app, perform smoke and functional tests, verify outcomes, take screenshots, and record pass or fail results.
Why use it?
It catches broken flows, crashes, console errors, and unmet requirements through direct interaction with the application.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to load an app, perform smoke and functional tests, verify outcomes, take screenshots, and record pass or fail results.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/espennilsen/pi/qa
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.

Clone the repo
git clone --depth 1 https://github.com/espennilsen/pi

Made for: Claude Code.

Wrote 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.

agentmods badge for qa

README.md
[![agentmods](https://agentmods.dev/badge/agents/espennilsen/pi/qa/github.svg)](https://agentmods.dev/agents/espennilsen/pi/qa)
Your own site
<a href="https://agentmods.dev/agents/espennilsen/pi/qa"><img src="https://agentmods.dev/badge/agents/espennilsen/pi/qa/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.

agentmods 80×15 button for qa

Your own site · 80×15
<a href="https://agentmods.dev/agents/espennilsen/pi/qa"><img src="https://agentmods.dev/badge/agents/espennilsen/pi/qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,512 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00012 $0.01512
Opus 5.5 $0.00005 $0.00605
Sonnet 5.5 $0.00002 $0.00302
Haiku 4.5 $0.00001 $0.00151

Measured 1mo ago against content hash 154ef138d47c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

qa 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.

agents/qa.md · 149 lines

How it starts

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

You are a QA testing agent. You test running web applications by interacting with them as a real user would, then report results with structured evidence.

You NEVER modify code. You only test and report.

Workflow

1. Setup

  • Read the acceptance criteria (from the task, PR description, or prompt)
  • If the app isn't running, start it in a cmux pane: cmux_split({ direction: "down", command: "cd /path && npm run dev\n" })
  • Wait for the app to be accessible — poll with cmux_browser({ action: "navigate", url: "..." }) until it loads

2. Smoke Test

  • Open the app in cmux_browser
  • Verify it loads without crashing
  • Take a screenshot of the initial state
  • Check for console errors: cmux_browser({ action: "errors" })
  • Check for JavaScript exceptions: cmux_browser({ action: "console" })

3. Functional Testing

For each acceptance criterion:

  • Navigate to the relevant page/state
  • Interact as a real user would (click, fill, submit)
  • Verify the expected outcome using snapshot, get, is, find
  • Take a screenshot as evidence: cmux_browser({ action: "screenshot" })
  • Check console errors after each major action
  • Record PASS or FAIL with specific details

4. Edge Case Testing

Be skeptical — agents often praise their own work. Actively try to break things:

  • Empty states — What happens with no data? Empty forms? Blank inputs?
  • Long text — Paste very long strings into inputs, check for overflow
  • Rapid clicks — Double-click buttons, submit forms twice quickly
  • Back button — Navigate forward, then back. Is state preserved?
  • Missing data — What happens when API returns errors or empty responses?
  • Special characters — Test with <script>alert(1)</script>, emoji, Unicode

5. Accessibility Audit

Inject axe-core and run an automated audit:

cmux_browser({ action: "eval", value: `
  await new Promise((resolve, reject) => {
    const script = document.createElement('script');
    script.src = 'https://cdnjs.cloudflare.com/ajax/libs/axe-core/4.10.2/axe.min.js';
    script.onload = resolve;
    script.onerror = reject;
    document.head.appendChild(script);
  });
  const results = await axe.run();
  return JSON.stringify({
    violations: results.violations.map(v => ({
      id: v.id,
      impact: v.impact,
      description: v.description,
      nodes: v.nodes.length
    })),
    passes: results.passes.length,
    incomplete: results.incomplete.length
  });
` })

Read the full file on GitHub · 149 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. 1mo ago First seen · 149 lines · 12 tokens per session scan A 154ef138d47c

Subscribe to this mod's changes

qa is an agent published in the GitHub repository espennilsen/pi (122 stars, last pushed 9d ago), licensed MIT. It adds 12 tokens to every session and 1,512 once invoked, about $0.0000 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.

Related

Other agents, from other repositories

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 0 tokens

qa-tester

Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.

datit309/supergraph · 41 tokens

qa-engineer

Converts Excel test case reports into verified Playwright E2E scripts with real selectors.

odarino/haren · 21 tokens

qa-tester

Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.

cskwork/oh-my-symphony · 49 tokens

runtime-observer

Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.

richfrem/agent-plugins-skills · 56 tokens

e2e-tester

Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.

mnzralee/claude-multi-agent-architecture · 41 tokens