qa

A command for checking a website through a real browser, including screenshots and assertions about what users can see and do. It supports actions such as opening pages, clicking, filling fields, and checking text or URLs.

In plain words
What is it for?
Use it for browser smoke tests, acceptance testing, forms, navigation, login flows, and other complete user journeys.
Why use it?
It finds failures in real browser behavior instead of only checking source code or isolated tests. A pass requires observable evidence from the tested flow.

Command

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.

agentmods
npx agentmods add commands/mtthsnc/tempest/qa
Clone the repo
git clone --depth 1 https://github.com/mtthsnc/tempest
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 141 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00014 $0.00141
Opus 5 $0.00007 $0.00071
Sonnet 5 $0.00003 $0.00028
Haiku 4.5 $0.00001 $0.00014

Measured yesterday against content hash 87bf417a723e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

plugins/tempest/commands/qa.md · 13 lines

What it actually says

Load and follow the qa skill to verify the change through the real browser UI via agent-browser.

What to QA: $ARGUMENTS

Work through the skill's procedure end to end: open the page, snapshot the interactive tree, interact using current refs, assert the observable outcome, and save a screenshot. Report PASS only on verified evidence; on failure, capture a repro and add a regression test. Prefer the native agent_browser tool if available, otherwise drive the agent-browser CLI via the shell.

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. yesterday First seen · 13 lines · 14 tokens per session scan A 87bf417a723e

Subscribe to this mod's changes

qa is a command published in the GitHub repository mtthsnc/tempest (2 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 141 once invoked, about $0.0001 per session on Opus 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.