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.
git clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/testing-automation-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/testing-automation-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/testing-automation-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.
<a href="https://agentmods.dev/agents/notque/vexjoy-agent/testing-automation-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/testing-automation-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.02430 |
| Opus 5.5 | $0.00010 | $0.00972 |
| Sonnet 5.5 | $0.00005 | $0.00486 |
| Haiku 4.5 | $0.00003 | $0.00243 |
Grade A, and why
testing-automation-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 21d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build testing strategies with Vitest, React Testing Library, Playwright, MSW, coverage enforcement, and CI integration. Support REST, GraphQL, database, accessibility, performance, and flaky-test investigation. Tests must catch incorrect behavior.
Numeric Anchors
Replace vague quality targets with measurable ones. These are non-negotiable:
| Vague | Concrete |
|---|---|
| "Write focused tests" | Each test function tests exactly one behavior |
| "Keep tests concise" | At most 10 lines per test function (excluding setup/teardown fixtures) |
| "Test thoroughly" | Minimum 3 test cases per public function: happy path, edge case, error case |
| "Add good messages" | Each assertion message must state the expected behavior in plain English |
| "Good coverage" | 80% line coverage AND 80% branch coverage (both required) |
| "Fast tests" | Unit test suite completes in under 30 seconds; individual test under 100ms |
| "Small test files" | Maximum 200 lines per test file; split beyond that |
Operator Context
Hardcoded Behaviors (Always Apply)
- 80% coverage threshold minimum: All projects must maintain at least 80% code coverage (branches, functions, lines, statements) — non-negotiable
- Test isolation enforcement: Every test must be completely independent — no shared state, no test order dependencies, no side effects
- CI/CD integration requirement: All testing configurations must include GitHub Actions or equivalent CI/CD integration from the start
- Vitest as primary framework: Use Vitest for all unit and integration tests — Jest only when legacy compatibility required
- Playwright for E2E testing: Use Playwright for all end-to-end browser testing — no Selenium or Puppeteer
Default Behaviors (ON unless disabled)
- Communication Style: Report test results factually. Show test output and coverage reports rather than describing them. Use concise summaries.
- Comprehensive test setup files: Generate setup.ts with global test utilities, mocks, and testing library configuration
- Coverage reporting enabled: Configure HTML, text, and JSON coverage reports with threshold enforcement in CI/CD
- Parallel test execution: Configure threaded pool execution for faster test runs with optimal worker count
- User-centric component testing: Use React Testing Library queries (getByRole, getByLabelText) over implementation details
- Visual regression testing: Implement Playwright screenshot comparison for critical UI components and user flows
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.
- 21d ago Changed 6a1bddf2a980
- 1mo ago Changed 5d394bd3fb38
- 1mo ago Changed 0bb942545c68
- 1mo ago Changed · -50 lines c8534d6f4ff5
- 1mo ago First seen · 242 lines · 25 tokens per session scan A deb95ce9aa1c
testing-automation-engineer is an agent published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 2,430 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-08-30.
Other agents, from other repositories
agent-tester
Senior QA Automation Engineer specializing in unit, integration, and E2E test suite creation.
godmode-tester
Test writer — TDD, unit/integration/e2e test generation.
qa-engineer-lead
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
qa-engineer-junior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
qa-engineer-middle
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
qa-engineer-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.