awesome-agv: Agent for Claude Code

.agents/agents/test-automation-engineer.md

test-automation-engineer is an agent for Claude Code from irahardianto/awesome-agv. It costs 53 tokens per session (1,544 once invoked), scanned A, original, MIT.

A test automation agent that writes and maintains automated checks for user journeys, APIs, test data, accessibility, visual changes, and test infrastructure.

In plain words
What is it for?
Use it to build Playwright browser tests, API checks, fixtures, test environments, coverage reports, accessibility checks, and screenshot comparisons.
Why use it?
It helps detect regressions repeatedly and investigates tests that fail inconsistently, without changing production code.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: installed under .agents/ (shared by several agents).

This is irahardianto/awesome-agv's own configuration. It tells Claude Code how to work on awesome-agv itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything awesome-agv configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/irahardianto/awesome-agv/main/.agents/agents/test-automation-engineer.md
Clone the repo
git clone --depth 1 https://github.com/irahardianto/awesome-agv

Made for: Claude Code.

Wrote 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.

agentmods badge for test-automation-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/irahardianto/awesome-agv/test-automation-engineer/github.svg)](https://agentmods.dev/agents/irahardianto/awesome-agv/test-automation-engineer)
Your own site
<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.

agentmods 80×15 button for test-automation-engineer

Your own site · 80×15
<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>
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,544 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 10d ago against content hash 67585c4ff892, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/agents/test-automation-engineer.md · 115 lines

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)

  1. E2E testing — Playwright via MCP for UI, user journey validation for critical money paths only
  2. Test infrastructure — test runners, CI config, test environments, fixtures, flaky test investigation
  3. API testing — APIRequestContext, contract testing, load testing scaffolding, smoke tests
  4. Test data — API-seeded factories, dynamic data generation, cleanup, isolation strategies
  5. Test reporting — coverage reports, gap analysis, flaky test detection, regression tracking
  6. Accessibility testing — toMatchAriaSnapshot, @axe-core/playwright, keyboard navigation
  7. Visual regression — toHaveScreenshot baseline 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

  1. Receive scope card (suite domain + target feature)
  2. Discover app surfaces via MCP snapshot
  3. Write spec file (plan critical user journeys)
  4. Generate tests per spec (Generate phase below)
  5. Heal failures (Heal phase below)
  6. 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_command only when MCP lacks capability (tracing, video, browser install)
  • NEVER mix MCP and CLI in the same session
  • Load browser-automation skill for full tool reference, selector strategy, and assertion patterns

Read the full file on GitHub · 115 lines

Changes

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.

  1. 10d ago First seen · 115 lines · 53 tokens per session scan A 67585c4ff892

Subscribe to this mod's changes

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.