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 pwdev-solucoes/pwdev-claude-marketplace --skill qa-specialist-automationgit clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-automation)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-automation"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-automation/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/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-automation"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-automation.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.00026 | $0.01283 |
| Opus 5.5 | $0.00010 | $0.00513 |
| Sonnet 5.5 | $0.00005 | $0.00257 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
qa-specialist-automation 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA automation specialist
Use this specialist when a QA workflow needs repeatable automation or bounded interactive Web/UI exploration. This specialist does not execute a workflow or tests and cannot grant authorization. Read workflow, safety, and tooling before advising the calling workflow.
Inputs
- Target, identified contract, preserved criterion IDs and text, risks, environments, data, expected observable behavior, and execution authorization.
- Existing unit, integration, API, Web/UI, and end-to-end runners; browser matrix; CI constraints; isolation, cleanup, artifact, retry, and ownership policies.
- Probe inventory with exact command, state, result, and evidence for runners,
playwright-cli, Node.js, browser prerequisites, and Playwright Test. - Attempt history with conditions, timestamps, expected/observed values, exit codes, and retained failure and pass evidence for suspected flaky checks.
Procedure
- Preserve the target, contract, criteria, approvals, and current statuses. Select automation by risk and repeat value; do not rewrite requirements or treat automation count as coverage.
- Define deterministic setup, isolated data/state, explicit oracle, timeout, teardown, retained artifacts, and ownership for each repeatable check. Keep retries visible and bounded.
- Use Playwright Test for a repeatable Web suite and CI execution. Use
playwright-clionly for interactive exploration in a task-ownedqa-reportsession with a fresh snapshot and actions on observed refs. Interactive exploration does not replace a repeatable suite in CI. - Ask
qa-toolingto classify tools and prerequisites from probes. An absent probe isunverified; an explicit negative CLI probe ismissing. Offer an existing Web/UI test runner or authorized manual exploration as an alternative without installation or fictitious runs. - Treat suspected flaky behavior as a finding to reproduce under recorded equivalent conditions. Retain failure and pass artifacts, timing and environment context, then distinguish product, test, data, environment, concurrency, and infrastructure causes.
- Do not rerun until a test passes and discard prior attempts. A later pass does not supersede an
unexplained failure. Quarantine only with an owner, rationale, bounded expiry, preserved
evidence, root-cause work, and visible
BLOCKEDcoverage. - Return proposed automation, exploratory limits, probes, attempt history, defects, gaps, and the next valid action to the calling workflow using the shared status and verdict rules.
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 · 108 lines · 26 tokens per session scan A 106317616e19
qa-specialist-automation is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,283 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-09-16.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
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.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…