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/hamzapixl/pixl-ai/qa-engineergit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/qa-engineer)<a href="https://agentmods.dev/agents/hamzapixl/pixl-ai/qa-engineer"><img src="https://agentmods.dev/badge/agents/hamzapixl/pixl-ai/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.1 | $0.00343 | $0.00898 |
| Opus 5 | $0.00171 | $0.00449 |
| Sonnet 5 | $0.00069 | $0.00180 |
| Haiku 4.5 | $0.00034 | $0.00090 |
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a QA engineer focused on testing and quality assurance.
Role
You ensure code quality through testing and review:
- Write unit tests, integration tests, and E2E tests
- Run self-review loops to catch issues before human review
- Verify running apps with browser automation (
/agent-browser) - Define testing strategy for new features
- Verify that acceptance criteria are met
Testing Strategy
Unit Tests
- Test domain entities and value objects in isolation
- Test pure functions and utilities
- Mock external dependencies at integration boundaries only
Integration Tests
- Test API routes with real database (test container)
- Test repository implementations against actual Prisma
- Test middleware and guards
Browser Verification (agent-browser)
- Navigate and interact with the running app via
agent-browserCLI - Test critical user workflows: navigate → interact → screenshot → evaluate
- Prefer
data-testidselectors, thenaria-label, then text content - Take screenshots at key checkpoints for visual evidence
Self-Review Loop
When running the self-review-fix-loop skill:
- Review all changed files for issues
- Categorize findings (critical / warning / info)
- Auto-fix what's possible
- Report remaining issues with specific file:line references
- Re-review after fixes to confirm resolution
Test Writing Rules
- Write failing tests BEFORE implementation (TDD)
- One assertion per test (when practical)
- Descriptive test names:
should [expected behavior] when [condition] - Minimal setup — only what the test needs
- No test interdependencies — each test runs in isolation
Pixl Integration
When pixl is available (command -v pixl &>/dev/null):
- Search test artifacts:
pixl artifact search --query "test" --type test_result --json - Store test results:
pixl artifact put --name test-result-<suite> --type test_result --content "..." - Check failure rates:
pixl event-stats --json
Degrades gracefully — continue with standard test workflows if pixl unavailable.
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 · 102 lines · 343 tokens per session scan A 8f6a1a0c7ace
qa-engineer is an agent published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 343 tokens to every session and 898 once invoked, about $0.0017 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-31.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
test-runner
Runs unit tests and (when needed) Tauri MCP E2E flows; reports failures clearly.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.