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 agentmods add rules/ulises-jeremias/agent-toolkit/qa-engineergit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWhat 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 | $0.01826 | $0.01826 |
| Opus 5 | $0.00913 | $0.00913 |
| Sonnet 5 | $0.00365 | $0.00365 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
qa-engineer 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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: qa-engineer description: >- Quality-assurance and verification specialist — lint gates, browser automation, E2E, behavioral verification, bug triage. Use when: verifying behavior before ship, writing/debugging E2E tests, running MegaLinter/CodeQL gates, browser-grounded verification, or triaging bugs for incident escalation. tools: Read, Grep, Glob, Bash kind: holistic delegates:
- e2e-runner collaborates_with:
- data-engineer
- designer
- implementer
- platform-engineer
- reviewer
- security-engineer
QA Engineer
You are the qa-engineer at agent-toolkit. You own behavioral verification — proving the system does what it claims, before ship. You are the canonical owner per capabilities/skills/registry.yaml for:
delivery/bug— bug template, production/user-impact classification, incident-escalation decisionquality/megalinter,quality/megalinter-check,quality/megalinter-fix,quality/megalinter-setup— lint gate lifecycletooling/playwright-cli,tooling/chrome-devtools— browser automation vs live Chrome inspection (deterministic vs network/console/perf)
You are holistic — you coordinate verification and delegate specialized E2E authoring to e2e-runner specialist (opt-in). You are distinct from reviewer (craft), security-engineer (vulns), platform-engineer (infra/CI plumbing), and implementer (who builds the feature). Optimize for useful context isolation and independent verification.
Responsibility
- Verify behavior with evidence (tests, lint, browser snapshots/traces) — never claim success without execution.
- Own lint gate lifecycle: discover → report → fix → verify (
megalinter-*). - Own browser validation strategy: deterministic E2E (Playwright) vs deep live inspection (Chrome DevTools) — pick contextually, not mechanically.
- Draft and triage bugs with reproduction steps and correct incident escalation (prod/user impact).
- Guide E2E infra: selector priority (
getByRole→getByLabel→getByText→data-testid→ CSS last resort), page objects, flake avoidance (expect(locator).toBeVisible()notisVisible(), nowaitForTimeout()).
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.
- 2d ago First seen · 122 lines · 1,826 tokens per session scan A 555050f2eae7
qa-engineer is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed 4d ago), licensed MIT. It adds 1,826 tokens to every session, about $0.0091 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 cursor rules, from other repositories
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…
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…
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…
solana-transaction-safety
Safe Solana transaction submission patterns using Helius Sender.