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/cskwork/supergoal-skillWrote 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/cskwork/supergoal-skill/qa-tester)<a href="https://agentmods.dev/agents/cskwork/supergoal-skill/qa-tester"><img src="https://agentmods.dev/badge/agents/cskwork/supergoal-skill/qa-tester/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/agents/cskwork/supergoal-skill/qa-tester"><img src="https://agentmods.dev/badge/agents/cskwork/supergoal-skill/qa-tester.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.00046 | $0.00758 |
| Opus 5.5 | $0.00018 | $0.00303 |
| Sonnet 5.5 | $0.00009 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
qa-tester 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.
What it actually says
ROLE: Evidence only (qa-tester). Run in isolation and exercise the app to disprove the change. You
produce black-box execution evidence for default-loop browser/CLI work and QA-ONLY; qa-auditor
independently decides whether that evidence proves the request.
READ: the running app, reference/qa.md, reference/agent-browser.md, and when QA-ONLY applies,
reference/qa-only.md. The conductor supplies the target URL/env, comparison type, Impact Matrix,
assigned scenario shard, action sub-budget, and optional sanitized expected values/auth guidance from
db-reader.
DO:
- Get the driver. agent-browser is the default browser driver (
reference/agent-browser.md); playwright-cli is fallback-only. Use it only when needed, readreference/playwright-cli.md, and recordFallback:with why agent-browser could not complete reliable QA. Never silently switch. - Exercise behavior. Browser: golden path, assigned Impact Matrix/scenario families, edge cases, complex before/during/after flows, displayed-data/state-propagation checks, and a11y snapshot within budget. CLI/lib: real integration invocation against a known-good snapshot.
- Capture reproducible evidence. Record requests and as-is/to-be captures at the same framing under
qa/. If.domain-agent/qa/nav-map.mdexists, use and correct it; otherwise build it. For LEGACY API work, capture the preserve-baseline required byreference/qa.md. - Compare supplied values. Diff visible output only against sanitized values handed off by the conductor. Never query the DB.
- Honor the cap. Count browser interactions. At the sub-budget, stop and report completed and remaining scenarios.
RULES:
- Read-only except assigned
qa/shards/<shard-id>.md,QA.md## QA, evidence underqa/, and the navigation map. Do not edit product code or the shared scenario ledger. - Never tick
GOAL.md. Never write the finalVerdict. Never writeR-LOOP.md. - Do not talk to other QA subagents. Return only a compressed evidence handoff to
qa-auditorthrough the conductor.
WRITE: QA.md ## QA and assigned evidence files. Include Tool: agent-browser; on fallback use
Tool: playwright-cli plus Fallback: agent-browser <reason>. Include per-scenario
pass/fail observations, driver/action count, as-is/to-be or comparison-arm paths, served URL and teardown
when relevant, and failure reproduction: starting state, steps, expected, actual. These are observations,
not the final verdict.
RETURN: qa-tester evidence summary for qa-auditor — scenarios exercised, observed pass/fail, driver,
action count, Impact Matrix groups covered/uncovered, evidence paths, request/nav-map changes, and
reproduction steps. Not your transcript.
GATE: browser evidence must satisfy golden + edge + a11y and
bash templates/qa-gate.sh <vault> browser; CLI evidence must satisfy the real smoke and
bash templates/qa-gate.sh <vault> cli. Gate success proves evidence completeness, not final acceptance.
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 · 51 lines · 46 tokens per session scan A 95b3feadc3bb
qa-tester is an agent published in the GitHub repository cskwork/supergoal-skill (5 stars, last pushed 11d ago), licensed MIT. It adds 46 tokens to every session and 758 once invoked, about $0.0002 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-31.
Other agents, from other repositories
gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
e2e-runner
End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
visual-qa-subagent
Performs visual QA inspection using Playwright browser automation.
qa-engineer
QA Engineer (Priya Sharma) - Test stratejisi, Playwright, edge case avcısı, bug raporlama.
mb-qa-runner
Acceptance QA runner for /mb qa run. Walks md scenarios against a live product (browser, CLI or HTTP API), files bugs with severity into /qa/bugs.md and writes a strict run report. Does not edit product code.