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/verifygit 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/verify)<a href="https://agentmods.dev/commands/desplega-ai/qa-use/verify"><img src="https://agentmods.dev/badge/commands/desplega-ai/qa-use/verify.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.00158 |
| Opus 5 | $0.00003 | $0.00079 |
| Sonnet 5 | $0.00001 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
verify 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 3d 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:verify
Verify a feature works through automated browser testing.
Invokes skill: qa-use
Arguments
| Argument | Description |
|---|---|
description |
What to verify (e.g., "login works with valid credentials") |
What Happens
- Searches for existing tests matching your description
- If no test exists, offers to explore and create one
- Runs the test
- Reports results with specific fix recommendations
Examples
/qa-use:verify "login works with valid credentials"
/qa-use:verify "checkout flow completes successfully"
/qa-use:verify "form shows validation errors"
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.
- 3d ago First seen · 32 lines · 7 tokens per session scan A 060d6945d3a0
verify 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 158 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
audit
Run a full WCAG + NIST compliance audit with signed evidence pack.
bootstrap
Scan a page with alethiaproposetests then run each suggested block.
multi-page
Smoke test multiple pages in parallel using alethiatellparallel.
regression
Run a fixed assertion suite against a URL — fail on any regression.
safety-check
Verify the EA1 safety gate blocks all destructive actions on a page.
smoke
Quick Alethia smoke test — navigate and assert the page loads.