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/qawolfcliskill.template)<a href="https://agentmods.dev/commands/qawolf/cli/qawolfcliskill.template"><img src="https://agentmods.dev/badge/commands/qawolf/cli/qawolfcliskill.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/qawolfcliskill.template"><img src="https://agentmods.dev/badge/commands/qawolf/cli/qawolfcliskill.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.00112 | $0.02800 |
| Opus 5.5 | $0.00045 | $0.01120 |
| Sonnet 5.5 | $0.00022 | $0.00560 |
| Haiku 4.5 | $0.00011 | $0.00280 |
Grade A, and why
qawolf-cli 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 12d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Wolf CLI
qawolf runs QA Wolf flows locally, calls the QA Wolf public API, and drives
interactive runners: live cloud pods holding a browser you can see and act on.
This file is an overview, not a reference. Before first using a command whose
flags are not shown here, run qawolf <command> --help once. The installed CLI
is authoritative for flags and always matches its version; reuse that syntax
for the rest of the task.
Auth
Commands that talk to QA Wolf authenticate via the QAWOLF_API_KEY
environment variable (or stored credentials from qawolf auth login).
read and write commands require auth; local commands do not, unless
their table entry notes a flag that switches them to read.
Verify with qawolf auth whoami. Never print or log the key.
A team API key in the environment is the whole credential, including for the
runner group. Nothing needs a browser login, a session token or a held
connection, so a sandbox that can set one environment variable and make
requests to one host can do everything below.
Commands use https://app.qawolf.com by default. Set QAWOLF_HOST_URL to
target another deployment host, for example
https://app.staging.example.com. QAWOLF_API_URL is a separate API endpoint
and does not select the deployment host used by CLI commands.
Resolve the target environment once per task. Use QAWOLF_ENVIRONMENT when it
is set; otherwise select an id or alias from
qawolf --json environment find and reuse it. Shell invocations may not share
exported variables, so pass the selected environment explicitly instead of
rediscovering it. Check the command's help for its environment flag: variable
commands use --environment-id; qawolf flows run uses --env; and
qawolf runner run uses --env-id, which falls back to QAWOLF_ENVIRONMENT
when neither it nor --env-file is passed.
If multiple environments are returned and the task context does not identify the target, ask instead of guessing. Do not default to the newest environment.
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.
- 12d ago Changed · +3 lines 970ef3de804e
- 20d ago Changed · +2 lines daeaccb7d527
- 24d ago Changed · +1 lines 856fcd4f8605
- 1mo ago Changed · -6 tokens per session 054f5e451daa
- 1mo ago Changed · +54 lines 9cb2f94c4f10
- 1mo ago Changed · +6 lines 4aac4e36cbe1
- 1mo ago Changed · +3 lines bfa1ed43fbc5
- 1mo ago First seen · 145 lines · 118 tokens per session scan A d2edc62d2a66
qawolf-cli is a command published in the GitHub repository qawolf/cli (3,455 stars, last pushed 2d ago), licensed Apache-2.0. It adds 112 tokens to every session and 2,800 once invoked, about $0.0004 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.
Other commands, from other repositories
playwright-test-generate
Generate tests for the test plan's bullet 1. Adding Todos. Generate one test at a time, never in parallel.
playwright-test-coverage
Produce test coverage.
test
Run the app's microflow tests and verify it in the browser.
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.
check-ux
Walk the key flows in a real browser at mobile and desktop viewports, then a task per friction point.
create-smoke-test.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.