What is test-automation-engineer?

An AI agent focused on testing software through user-like checks and test infrastructure. E2E tests are full user-flow tests, while API tests check services directly.

Use it to write Playwright browser tests, API and accessibility checks, test data setup, coverage reports, visual comparisons, and flaky-test investigations.

It separates test work from production-code work and helps investigate failures without mixing responsibilities.

How irahardianto/rugged-gemini configures Claude Code and Gemini CLI

Reuse

Borrowing it

Nothing to install: this file belongs to irahardianto/rugged-gemini. 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/rugged-gemini/main/.gemini/agents/test-automation-engineer.md

Clone the repo

git clone --depth 1 https://github.com/irahardianto/rugged-gemini

Made for: Claude Code, Gemini CLI.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/irahardianto/rugged-gemini/test-automation-engineer/github.svg)](https://agentmods.dev/agents/irahardianto/rugged-gemini/test-automation-engineer)

Your own site

<a href="https://agentmods.dev/agents/irahardianto/rugged-gemini/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/rugged-gemini/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/irahardianto/rugged-gemini/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/rugged-gemini/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,400 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 91% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00053	$0.01400
Opus 5.5	$0.00021	$0.00560
Sonnet 5.5	$0.00011	$0.00280
Haiku 4.5	$0.00005	$0.00140

Measured 1mo ago against content hash 5632feecfdcd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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

This is a copy

91% identical to test-automation-engineer — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.gemini/agents/test-automation-engineer.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 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 — toHaveScreenshot baseline management, environment-stable CI capture

Skills

Load from .gemini/skills/ as needed: browser-automation, research-methodology, sequential-thinking

Boundaries (DO NOT CROSS)

No production code. No unit tests (implementation teams own those). No code review (that's QA Analyst). No architecture decisions. No security audits. No debugging sessions (that's QA Analyst).

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

Spec-Driven Testing Workflow

Phase 1: Plan

Explore app via mcp_playwright_browser_snapshot — inventory interactive surfaces
Map critical user journeys only (money paths): edge cases, validation errors, persistence
Write spec file: specs/<feature>.plan.md
- Each scenario: independent, starts from clean state, kebab-case name
- Steps at user level ("Type 'Buy milk' into the input"), not API level
- Observable outcomes as - expect: bullets → become assertions
- File path per scenario: tests/e2e/<group>/<scenario>.spec.ts
Apply coverage strategy: E2E only for flows that cross system boundaries or have direct business impact

Read the full file on GitHub · 98 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.

1mo ago First seen · 98 lines · 53 tokens per session scan A 5632feecfdcd

Subscribe to this mod's changes

test-automation-engineer is an agent published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 1,400 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to test-automation-engineer, differing in 21 lines, and is treated as a copy.

E2E testing Testing

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 0 tokens

rugged-gemini: Agent for Claude Code