QA Wolf CLI is a command-line tool for running and managing QA Wolf end-to-end testing flows from a local terminal or continuous-integration environment. Development and QA teams use it to execute their browser-test flows, while test creation, AI test generation, cloud execution, and collaboration belong to the wider QA Wolf platform.
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/qawolf/cliWrote 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/commands/qawolf/cli/qawolfclirunresults.template)<a href="https://agentmods.dev/commands/qawolf/cli/qawolfclirunresults.template"><img src="https://agentmods.dev/badge/commands/qawolf/cli/qawolfclirunresults.template/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/commands/qawolf/cli/qawolfclirunresults.template"><img src="https://agentmods.dev/badge/commands/qawolf/cli/qawolfclirunresults.template.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.00000 | $0.02030 |
| Opus 5.5 | $0.00000 | $0.00812 |
| Sonnet 5.5 | $0.00000 | $0.00406 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
qawolfCliRunResults.template 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 21d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| xargs -r curl -sS -o trace.zip How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reading a run's results
How to use what qawolf run get --run-id <id> --json returns, and how to read
the Playwright trace it links to.
Call run get with --json and you see most of the response immediately. Read
this file for the parts a single response cannot show you: fields that appear
only when something fails, rules about the artifact URLs, and how to read a
trace without opening the trace viewer.
Start with the failed flows
A run of a whole suite can hold hundreds of flows, and the full response then runs to hundreds of kilobytes: more than a shell shows you, and more than any investigation needs. The interesting part is a handful of failed flows, so ask for those first:
qawolf run get --run-id "$RUN_ID" --flow-statuses failed --json
--flow-statuses takes one or more of queued, running, passed, failed
and canceled, separated by spaces (--flow-statuses failed canceled), and
keeps only the flows whose status matches. The run-level fields (status,
blockingBugCount, git, url) still describe the whole run, so a filtered
read tells you both how the run went and which flows to look at. Widen the
filter, or drop it, only when you need the other flows too.
A flow that failed and then passed on a retry has status passed, so a
failed-only read leaves it out. If the flow you were asked about passed on a
retry, add passed to the filter and read its earlier attempts. For a flow
that is still queued, running or was canceled, widen the filter or drop it.
Do not save the full response to a file and script over it to find the failed flows. The filter answers that in one call.
The shape
A run holds flows, a flow holds attempts, and artifacts hang off an attempt:
run
└── flows[]
├── failure only when the flow failed
└── attempts[] oldest first
├── logsUrl
├── traceUrl
└── videoUrl
runId in the response is canonical and can differ from the id you asked for.
Use the returned value for follow-up calls.
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.
- 21d ago Changed · +2 lines a7f2ed1445ad
- 24d ago Changed · +26 lines c4ed494bc168
- 1mo ago Changed · +8 lines c4cea4346bf6
- 1mo ago First seen · 149 lines · 0 tokens per session scan A 5a8d8074c983
qawolfCliRunResults.template is a command published in the GitHub repository qawolf/cli (3,456 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,030 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
playwright-test-plan
Create test plan for basic operations of the todo app. Test plan should contain around 20 tests.
playwright-test-heal
Run all my tests and fix the failing ones.
test-integration.en
Run the integration test workflow.
test-bar
Generate a floating QA test overlay for the current branch's UI changes. Use when user says /test-bar, needs visual QA scenarios, or wants to test conditional rendering paths.
auto-canary
A command for deployment verification that runs a build, end-to-end tests, and browser health checks. End-to-end tests check a complete user flow across the application rather than only one small part.
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.