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 agents/vibeeval/vibecosystem/qa-engineergit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/agents/vibeeval/vibecosystem/qa-engineer)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/qa-engineer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/qa-engineer.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.01055 |
| Opus 5 | $0.00015 | $0.00528 |
| Sonnet 5 | $0.00006 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00105 |
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 yesterday.
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 — 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.
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.
- yesterday First seen · 93 lines · 30 tokens per session scan A 79ab47d2de54
qa-engineer is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 27d ago), licensed MIT. It adds 30 tokens to every session and 1,055 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
stagehand-expert
Use this agent when you need executable Stagehand test files for TDD workflow. ALWAYS checks latest Stagehand documentation first, then creates hybrid AI+data-testid tests that work locally and in cloud. Expert in LOCAL vs BROWSERBASE modes, proper API usage (stagehand.page.act/observe), and fallback strategies for…
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
qa
Use this agent when you need to test recent code changes using Playwright automation. Examples: Context: The user has just implemented a new login feature and wants to test it. user: "I just added a new login validation feature, can you test it?" assistant: "I'll use the qa agent to test your recent changes with…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.