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.
npx agentmods add commands/desplega-ai/qa-use/recordgit clone --depth 1 https://github.com/desplega-ai/qa-useWrote 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/desplega-ai/qa-use/record)<a href="https://agentmods.dev/commands/desplega-ai/qa-use/record"><img src="https://agentmods.dev/badge/commands/desplega-ai/qa-use/record.svg" alt="Measured on agentmods" 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 | $0.00007 | $0.00369 |
| Opus 5 | $0.00003 | $0.00185 |
| Sonnet 5 | $0.00001 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
record 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 4d 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
/qa-use:record
Record browser interactions and generate test YAML, or edit existing tests with AI assistance.
Invokes skill: qa-use
Arguments
| Argument | Description |
|---|---|
start [name] |
Start recording with optional test name |
edit <test-name> |
AI-assisted editing of existing test |
stop |
Stop recording and generate test YAML |
What Happens
Recording Mode (start/stop)
- start: Creates browser session, enters recording mode
- actions: You perform browser commands, they're tracked
- stop: Generates test YAML with variables and semantic descriptions
- save: Writes to
qa-tests/<name>.yaml
Edit Mode (edit)
- Loads existing test definition
- Understands your desired changes
- Applies modifications
- Validates and saves with confirmation
Examples
Recording a new test
/qa-use:record start login-test
# ... perform browser actions ...
/qa-use:record stop
Editing an existing test
/qa-use:record edit login-test
Recording from Logged-In State
To record a test that assumes the user is already logged in, first create a session with --after-test-id:
# Create session that runs login test first
qa-use browser create --after-test-id <login-test-uuid>
# Then start recording from the authenticated state
/qa-use:record start dashboard-test
This is useful for recording tests that depend on authentication without including login steps in every test.
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.
- 4d ago First seen · 65 lines · 0 tokens per session scan A 8e5a8271d62e
record is a command published in the GitHub repository desplega-ai/qa-use (27 stars, last pushed 3mo ago), licensed MIT. It adds 7 tokens to every session and 369 once invoked, about $0.0000 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-30.
Other commands, from other repositories
qa
Dispatch a verifiable browser task to the qa-tester subagent. Use for regression checks, smoke tests, and any task with a clean pass/fail outcome. Supports an EXHAUSTIVE mode that verifies every control behind an honesty gate.
record-workflow
Record browser interactions and generate a Playwright test with assertions and best-practice selectors.
chrome
Check Chrome Actuator connection and remind how to install the native host.
naive-test
Drive the live app as a naive first-time user and report UX/behavior gaps before deploy.
run
Run E2E tests and analyze results with screenshots and network drill-down.
audit
Run a full WCAG + NIST compliance audit with signed evidence pack.