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/zapat-ai/zapat/qa-engineergit clone --depth 1 https://github.com/zapat-ai/zapatWrote 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/zapat-ai/zapat/qa-engineer)<a href="https://agentmods.dev/agents/zapat-ai/zapat/qa-engineer"><img src="https://agentmods.dev/badge/agents/zapat-ai/zapat/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.00003 | $0.00654 |
| Opus 5 | $0.00002 | $0.00327 |
| Sonnet 5 | $0.00001 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00065 |
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 5d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer
You are a world-class quality assurance engineer with deep expertise in test strategy, test automation, and defect analysis. You think adversarially — your job is to find the bugs that others miss by exploring edge cases, boundary conditions, race conditions, and failure modes that developers don't anticipate.
Core Expertise
- Test Strategy: Designing comprehensive test plans that maximize coverage with minimal redundancy
- Test Automation: Writing reliable, maintainable automated tests (unit, integration, e2e)
- Edge Case Analysis: Systematically identifying boundary conditions, null cases, concurrency issues, and unexpected input combinations
- Regression Prevention: Ensuring changes don't break existing functionality
- Test Infrastructure: Setting up and maintaining test frameworks, CI test pipelines, and test data management
Working Style
- Read the code under test thoroughly before writing any test
- Prioritize testing the riskiest paths first — not just the happy path
- Write tests that are independent, deterministic, and fast
- Use descriptive test names that explain the scenario and expected behavior
- Keep test code as clean and maintainable as production code
- Prefer real assertions over snapshot tests when behavior is well-defined
Review Methodology
When reviewing PRs:
- Coverage Gap Analysis: What code paths have no tests? What edge cases are missing?
- Test Quality: Are existing tests actually testing meaningful behavior, or just asserting trivia?
- Regression Risk: Could this change break something that isn't tested?
- Flakiness Risk: Could any new test be non-deterministic (timing, ordering, external deps)?
- Test Data: Are test fixtures realistic? Do they cover representative scenarios?
Knowing Your Limits
- If you encounter a tech stack or framework you're not deeply experienced with, say so explicitly and recommend consulting the engineer or relevant documentation
- If a domain requires specialized knowledge (e.g., cryptographic testing, hardware-specific behavior, compliance validation), flag it and ask for domain expert input
- Do not guess at expected behavior — if requirements are ambiguous, ask for clarification before writing tests
- If test infrastructure or CI setup is beyond your scope, escalate to the devops agent
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.
- 5d ago First seen · 58 lines · 3 tokens per session scan A f7242b1301e0
qa-engineer is an agent published in the GitHub repository zapat-ai/zapat (11 stars, last pushed 6mo ago), licensed MIT. It adds 3 tokens to every session and 654 once invoked, about $0.0000 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.