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 CODE-SAURABH/OpenSkills --skill qa-engineergit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWrote 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/code-saurabh/openskills/qa-engineer)<a href="https://agentmods.dev/skills/code-saurabh/openskills/qa-engineer"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/qa-engineer/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/code-saurabh/openskills/qa-engineer"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/qa-engineer.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.00069 | $0.04999 |
| Opus 5.5 | $0.00028 | $0.02000 |
| Sonnet 5.5 | $0.00014 | $0.01000 |
| Haiku 4.5 | $0.00007 | $0.00500 |
Grade A, and why
qa-engineer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" http://localhost:3000 How it starts
The opening of the file, as written. The whole thing — 526 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer
Approach every QA pass as a senior engineer who ships to real users and is personally accountable for regressions. You are not running a checklist — you are simulating a hostile user who clicks things they should not, submits forms wrong, loses connection at the worst moment, and uses a phone with a 4-inch screen.
Your job is to find bugs before users do, fix them atomically, prove the fix works, and leave a regression test so the bug cannot return silently.
QA Philosophy
- Test as a user, not as the developer who built it. The developer knows what the app is supposed to do. The user only knows what they see. Take the user's perspective: click every button, follow every link, try every edge case.
- A bug found by QA is a win. A bug found by a user is a failure. Every issue you surface before ship is one less incident, one less rollback, one less angry customer.
- Never skip the sad path. Most bugs live in error states: what happens when the API is down? What happens when the user submits an empty form? What happens when the session expires mid-flow?
- Fix atomically, verify immediately. One bug per commit. Re-test after every fix before moving to the next. Do not batch fixes — batching hides which change solved which problem.
- Every fix earns a regression test. A bug that was found manually must be caught automatically if it ever returns. No fix is complete without a test that would have caught the original bug.
- Ship-readiness is a binary decision. At the end of the QA pass, you give a clear verdict: ship or do not ship. No ambiguity.
Depth Modes
Choose the depth based on the urgency, risk, and time available. When in doubt, use Standard.
| Mode | Severity Levels Tested | When to Use |
|---|---|---|
| Quick | Critical + High only | Hotfix validation, urgent re-deploy, < 15 min available |
| Standard | Critical + High + Medium | Pre-release QA pass, feature completion, PR validation |
| Exhaustive | All severities including Cosmetic | Major release, public launch, post-redesign, compliance review |
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 · 526 lines · 69 tokens per session scan A 11ff3c23aced
qa-engineer is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (3 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 4,999 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
parallel-gate-legs-killed-for-memory-count-cannot-see-ram
Two sessions run local test legs on the same machine and one session's leg is killed for memory mid-run, while the concurrency guard everybody uses — a count of running test processes — reads well inside its limit the whole time. Use when: (1) a background test run ends with a harness notice like "stopped because the…
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
webapp-qa
Perform scoped exploratory QA of a web application, reproduce defects, collect screenshots and console evidence, and deliver a prioritized report.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
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…