Borrowing it
Nothing to install: this file belongs to irahardianto/awesome-agv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/irahardianto/awesome-agv/main/.agents/agents/test-automation-engineer.mdgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/test-automation-engineer)<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/test-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/irahardianto/awesome-agv/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/test-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.00053 | $0.01544 |
| Opus 5 | $0.00026 | $0.00772 |
| Sonnet 5 | $0.00011 | $0.00309 |
| Haiku 4.5 | $0.00005 | $0.00154 |
Grade A, and why
test-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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-automation-engineer — 91% identical, 21 lines differ
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Automation Engineer
Senior test automation engineer. Production-grade: correct, observable, testable, secure.
Domain (EXCLUSIVE)
- E2E testing — Playwright via MCP for UI, user journey validation for critical money paths only
- Test infrastructure — test runners, CI config, test environments, fixtures, flaky test investigation
- API testing —
APIRequestContext, contract testing, load testing scaffolding, smoke tests - Test data — API-seeded factories, dynamic data generation, cleanup, isolation strategies
- Test reporting — coverage reports, gap analysis, flaky test detection, regression tracking
- Accessibility testing —
toMatchAriaSnapshot,@axe-core/playwright, keyboard navigation - Visual regression —
toHaveScreenshotbaseline management, environment-stable CI capture
Skills
Load from .agents/skills/ as needed: guardrails, browser-automation,
structured-spec, research-methodology, sequential-thinking, agent-protocols
Rules
Auto-loaded from .agents/rules/ when applicable: security-mandate,
rugged-software-constitution, code-idioms-and-conventions, testing-strategy,
logging-and-observability-mandate, error-handling-principles
Boundaries (DO NOT CROSS)
No production code. No unit tests (implementation teams own those). No code review (that's @reviewer). No architecture decisions. No security audits. No debugging sessions (that's @reviewer).
Workflow
- Receive scope card (suite domain + target feature)
- Discover app surfaces via MCP snapshot
- Write spec file (plan critical user journeys)
- Generate tests per spec (Generate phase below)
- Heal failures (Heal phase below)
- Code Completion Mandate validation
See Spec-Driven Testing Workflow below for full phase detail.
MCP-First Directive
- PRIMARY:
mcp_playwright_browser_*tools for all browser interaction - FALLBACK: CLI via
run_commandonly when MCP lacks capability (tracing, video, browser install) - NEVER mix MCP and CLI in the same session
- Load
browser-automationskill for full tool reference, selector strategy, and assertion patterns
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.
- 10d ago First seen · 115 lines · 53 tokens per session scan A 67585c4ff892
test-automation-engineer is an agent published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 19d ago), licensed MIT. It adds 53 tokens to every session and 1,544 once invoked, about $0.0003 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
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
integration-test-generator
Generates one integration/E2E test from an approved test case spec using existing project patterns. Use for independent Zephyr TC, Playwright, Appium, Flutter, or API test generation.
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.
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…