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/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/explore)<a href="https://agentmods.dev/commands/desplega-ai/qa-use/explore"><img src="https://agentmods.dev/badge/commands/desplega-ai/qa-use/explore/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/desplega-ai/qa-use/explore"><img src="https://agentmods.dev/badge/commands/desplega-ai/qa-use/explore.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.00007 | $0.00341 |
| Opus 5.5 | $0.00003 | $0.00136 |
| Sonnet 5.5 | $0.00001 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
explore 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 1mo 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:explore
Explore a web page or complete a navigation goal.
Invokes skill: qa-use
Arguments
| Argument | Description |
|---|---|
url |
URL to explore (e.g., https://example.com) |
goal |
Navigation goal (e.g., "find the pricing page") |
What Happens
- Creates browser session (or uses existing one)
- Navigates to the URL
- Analyzes page using accessibility snapshots
- Reports elements, navigation options, content found
Examples
/qa-use:explore https://example.com
/qa-use:explore "find the pricing page"
/qa-use:explore https://myapp.com/dashboard "find user settings"
Starting After Login
Many pages require authentication. Use --after-test-id when creating the browser session to start from a logged-in state:
# Create session that runs login test first
qa-use browser create --after-test-id <login-test-uuid>
# Then explore the authenticated area
/qa-use:explore https://myapp.com/dashboard
This is extremely useful for:
- Exploring authenticated pages - bypass login walls automatically
- Testing user-specific features - start as a logged-in user
- Complex setup flows - run a setup test, then explore manually
To get test UUIDs, use qa-use test run --list or check your tests in the desplega.ai dashboard.
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.
- 1mo ago First seen · 52 lines · 7 tokens per session scan A 82a65069ab8e
explore is a command published in the GitHub repository desplega-ai/qa-use (27 stars, last pushed 20d ago), licensed MIT. It adds 7 tokens to every session and 341 once invoked, about $0.0000 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
screenshot
Open a URL and take a screenshot to confirm the page renders.
console-errors
Open a URL and collect all console errors and failed network requests.
smoke-test
Smoke-test a user flow at a URL and verify the expected result.
generate-apple-doc
Navigate apple.com, add iPhone 17 to cart, and generate a documented tool-use example with token analysis.
check-browser
Use Browser Controller to check what's currently showing in my browser.
chrome
Check Chrome Actuator connection and remind how to install the native host.