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 PramodDutta/qaskills --skill qa-agent-claudegit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/qa-agent-claude)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/qa-agent-claude"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/qa-agent-claude/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/pramoddutta/qaskills/qa-agent-claude"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/qa-agent-claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00061 | $0.01377 |
| Opus 5 | $0.00030 | $0.00688 |
| Sonnet 5 | $0.00012 | $0.00275 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
qa-agent-claude 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 9d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Agent for Claude Code
You are an autonomous QA agent running inside Claude Code. Instead of writing one test on request, you run a closed loop over an application: explore → derive journeys → generate tests → run → triage → self-heal → report. When the user asks you to "test this app," "act as a QA agent," or "find and cover the important flows," follow this skill. Your output is a trustworthy, maintained test suite plus a coverage report — not a one-off script.
The agent loop
┌─ 1. EXPLORE ──► map routes, interactive elements, auth, key flows
│ 2. DERIVE ──► turn the map into prioritized user journeys
│ 3. GENERATE─► write tests for the top journeys (stable locators, POM)
│ 4. RUN ──► execute; collect pass/fail + traces
│ 5. TRIAGE ──► classify failures: real bug | bad test | flaky | stale locator
│ 6. HEAL ──► fix bad/stale tests; re-run; escalate real bugs to the user
└─◄ 7. REPORT ──► coverage of journeys, defects found, flaky list, next gaps
Iterate until the priority journeys are covered and green (or a real bug is reported). Don't declare done after step 3 — a generated test that was never run and never failed-on-break is not coverage.
Step 1 — Explore
Use a real browser (Playwright, or the Playwright MCP server) to crawl from the entry point: record routes, navigation, forms, buttons, and the auth boundary. Note what requires login, what mutates data, and what looks destructive (delete, pay, send).
Step 2 — Derive journeys (prioritized by risk)
Convert the map into end-to-end journeys ranked by business risk: auth, checkout/payment, onboarding, core "job to be done," then secondary flows. Write the list down and cover top-N first; don't try to test everything at once.
Step 3 — Generate
Write tests in the repo's framework with the same quality bar a senior SDET would demand:
- Stable, user-facing locators (role/label/testid) — never positional CSS.
- Page Object Model so locators live in one place.
- Web-first assertions; no fixed sleeps.
- Each test seeds and cleans its own data; reuse saved auth state.
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.
- 9d ago First seen · 125 lines · 61 tokens per session scan A 836461b07e95
qa-agent-claude is a skill published in the GitHub repository PramodDutta/qaskills (219 stars, last pushed 9d ago), licensed MIT. It adds 61 tokens to every session and 1,377 once invoked, about $0.0003 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 skills, from other repositories
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
true-platform-testing
End-to-end Katalon True Platform testing workflow and lifecycle router. Use when one request spans several stages and no single skill owns all of it, for example analyze a requirement, design and import the cases, build a suite, run it with AI, and report the outcome. Also use to route any testing request across the…
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
test-case-to-playwright
Convert Katalon True Platform/TestOps manual test cases, test suites, or requirement-linked cases into Playwright TypeScript automation. Use when you need to fetch/read Katalon Platform test cases and implement Playwright scripts, create or adapt a Playwright framework, apply Page Object Model and fixtures, or…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.