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 skills add MigoXLab/webqa-agent --skill webqagit clone --depth 1 https://github.com/MigoXLab/webqa-agentWrote 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/skills/migoxlab/webqa-agent/webqa)<a href="https://agentmods.dev/skills/migoxlab/webqa-agent/webqa"><img src="https://agentmods.dev/badge/skills/migoxlab/webqa-agent/webqa/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/skills/migoxlab/webqa-agent/webqa"><img src="https://agentmods.dev/badge/skills/migoxlab/webqa-agent/webqa.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.00036 | $0.00337 |
| Opus 5.5 | $0.00014 | $0.00135 |
| Sonnet 5.5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
webqa 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
WebQA
Use WebQA when the user wants to test a website or page from a real user's perspective.
Route
- For a normal website, page, URL, feature, login, search, form, navigation, or core-flow test, read
references/mini-agent.md. - For MCP server installation, API key setup, IDE configuration, or environment variables, read
references/setup.md. - For authenticated testing with browser cookies, read
references/cookies.mdbefore running the test. - For API errors, execution timeouts, missing reports, worker-limit errors, or stuck executions, read
references/troubleshooting.md.
Defaults
- If the user provides a URL and no specific objective, run the default mini-agent task: verify the homepage loads, core entry points are visible, and the main interactions show no obvious errors.
- If the user describes a test objective but gives no URL, ask for the URL before running WebQA.
- Keep the task focused on one URL and one natural-language objective.
- Do not treat execution completion as test success; final pass/fail reporting must come from the test report or documented fallback logic.
Boundaries
- This public skill exposes WebQA's MCP quick-mode testing workflow.
- Do not promise future capabilities until their reference files exist.
- Do not load
cookies.md,setup.md, ortroubleshooting.mdduring a normal public-page test unless that context is needed.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 29 lines · 36 tokens per session scan A eef62cc0b427
webqa is a skill published in the GitHub repository MigoXLab/webqa-agent (234 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 337 once invoked, about $0.0001 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 skills, from other repositories
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
browser-qa
Drive a real headless browser against a locally-served web UI and capture screenshot evidence, reporting step-level PASS/FAIL/BLOCKED with extracted DOM text and console errors. Use when a phase on the docker QA image must exercise a rendered UI and attach screenshots — it complements the text-evidence verify/qa-test…
qa-testing
Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to QA a page or site, run a smoke test after a deploy, verify a page before launch, or run a regression sweep. Triggers on QA, QA sweep, smoke test, regression test, post-deploy…
web-ui-test
Test the IronClaw web UI using the Claude for Chrome browser extension.
using-win
Use when invoking win-device MCP tools to drive a Windows test machine (agent-fleet project) -- screenshot-and-click UI testing, long-running shell commands, file or process operations, or coordinating exclusive device use across multiple agents.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.