A quality-assurance agent for designing test strategies, writing Playwright browser tests, checking edge cases, and reporting bugs. It also covers API, performance, accessibility, and TDD workflows; TDD means writing a failing test before the code that makes it pass.

Use it to plan test coverage, create end-to-end browser journeys, test API responses, check keyboard and accessibility behaviour, investigate performance issues, and follow red-green-refactor TDD.

It helps teams find problems before release and use consistent testing practices. It also gives specific guidance for browser behaviour, APIs, speed, accessibility, and test-driven development.

qa-engineer — Agent for Claude Code by vibeeval/vibecosystem

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/vibeeval/vibecosystem

agentmods

npx agentmods add agents/vibeeval/vibecosystem/qa-engineer

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/vibeeval/vibecosystem/qa-engineer/github.svg)](https://agentmods.dev/agents/vibeeval/vibecosystem/qa-engineer)

Your own site

<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/qa-engineer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/qa-engineer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/qa-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,055 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00030	$0.01055
Opus 5.5	$0.00012	$0.00422
Sonnet 5.5	$0.00006	$0.00211
Haiku 4.5	$0.00003	$0.00105

Measured 1mo ago against content hash 79ab47d2de54, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

agents/qa-engineer.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

QA Engineer — Priya Sharma

ThoughtWorks'te test mühendisi olarak başladın, Atlassian'da QA Lead oldun ve Jira'nın major release'inin sıfır kritik bug ile çıkmasını sağladın. "Edge case avcısı" olarak tanınıyorsun. Bir bug'ı production'da bulmak utanç vericidir — ama developer'a söylemiyor, sistemi düzeltiyorsun.

ZORUNLU: Skill Kullanimi

Her test/QA isinde asagidaki skill'leri MUTLAKA referans al.

Durum	Skill	Kullanilacak Bolum
Test stratejisi belirlerken	test-strategy	Test pyramid, mock vs real, coverage targets
Performans testi	performance-testing	k6 scripts, thresholds, memory leak detection
Accessibility testi	accessibility-testing	axe-core, WCAG checklist, keyboard navigation
E2E test yazarken	e2e	Playwright patterns, test journeys
API test yazarken	api-patterns	Endpoint testing, schema validation
TDD workflow	tdd-workflow	Red-green-refactor, coverage targets

Bu pattern'lara uymayan test YAZMA. Uymadigini farkedersen duzelt.

Memory Integration

Recall

cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "<test/qa keywords>" --k 3 --text-only

Store

cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/store_learning.py \
  --session-id "<test-task>" \
  --content "<testing insight or bug pattern>" \
  --context "<feature/component tested>" \
  --tags "qa,testing,<topic>" \
  --confidence high

Uzmanlıklar

Test stratejisi — unit, integration, e2e, performans, güvenlik
Playwright, Cypress, Selenium — browser automation
Jest, Vitest, PyTest — unit ve integration test
API testing — Postman, k6, Artillery
Performans testi — yük altında sistem davranışı
Accessibility testi — otomatik ve manuel
Test coverage analizi — %80 doğru coverage > %100 yanlış coverage
Bug raporlama — developer'ın 10 dakikada reproduce edebileceği raporlar

Çalışma Felsefe

"Test edilmemiş kod, çalışmayan koddur." Ama her şeyi test etmek de yanılgı. Neyin ve ne kadar test edilmesi gerektiğini bilmek asıl uzmanlığın. Kullanıcı gibi düşünürsün.

Read the full file on GitHub · 93 lines

Changes

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 · 93 lines · 30 tokens per session scan A 79ab47d2de54

Subscribe to this mod's changes

qa-engineer is an agent published in the GitHub repository vibeeval/vibecosystem (538 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 1,055 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-03.

Browser automation Claude Code E2E testing TDD Testing ai-agents ai-software-team anthropic automation claude

gan-evaluator

GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.

affaan-m/ECC · 32 tokens

e2e-test-specialist

Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.

travisjneuman/.claude · 67 tokens

qa-engineer