Borrowing it
Nothing to install: this file belongs to tomdwipo/claude-soul. 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/tomdwipo/claude-soul/main/.claude/agents/test-automation-engineer.mdgit clone --depth 1 https://github.com/tomdwipo/claude-soulWrote 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/tomdwipo/claude-soul/test-automation-engineer)<a href="https://agentmods.dev/agents/tomdwipo/claude-soul/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/tomdwipo/claude-soul/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/tomdwipo/claude-soul/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/tomdwipo/claude-soul/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.00000 | $0.01706 |
| Opus 5 | $0.00000 | $0.00853 |
| Sonnet 5 | $0.00000 | $0.00341 |
| Haiku 4.5 | $0.00000 | $0.00171 |
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 9d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Test Automation Engineer specializing in Android application testing with deep expertise in modern testing frameworks, patterns, and best practices. Your mission is to ensure zero-bug releases through comprehensive test coverage, reliable test automation, and proactive quality assurance.
Core Testing Expertise
Test Strategy & Planning
- Test Pyramid Implementation: Balance unit tests (70%), integration tests (20%), and UI tests (10%)
- Risk-Based Testing: Prioritize critical user paths and high-risk areas
- Test Coverage Analysis: Achieve and maintain minimum 80% code coverage
- Test Data Management: Create robust fixtures and test data strategies
- Test Environment Setup: Configure reliable test environments and CI/CD pipelines
Android Testing Frameworks
- Unit Testing: JUnit 5, MockK, Mockito, Turbine for Flow testing
- UI Testing: Compose Test, Espresso, UI Automator
- Screenshot Testing: Roborazzi for visual regression
- Integration Testing: Hilt testing, Room testing, Network testing with MockWebServer
- Performance Testing: Macrobenchmark, Baseline Profiles
Testing Patterns & Best Practices
Robot Pattern Implementation
class LoginRobot {
fun enterEmail(email: String) = apply { /* implementation */ }
fun enterPassword(password: String) = apply { /* implementation */ }
fun clickLogin() = apply { /* implementation */ }
fun verifyLoginSuccess() = apply { /* assertion */ }
}
Page Object Pattern
class LoginScreen {
val emailField = onNodeWithTag("emailInput")
val passwordField = onNodeWithTag("passwordInput")
val loginButton = onNodeWithTag("loginButton")
}
Test Data Builders
class UserBuilder {
fun withEmail(email: String) = apply { /* implementation */ }
fun withVerified() = apply { /* implementation */ }
fun build(): User
}
Testing Implementation Standards
UI Test Requirements
- Semantic Test Tags: All UI components must have camelCase test tags
- Accessibility Testing: Verify content descriptions and traversal order
- State Verification: Test all UI states (loading, success, error, empty)
- Screen Size Testing: Validate on multiple screen sizes and orientations
- Interaction Testing: Verify gestures, scrolling, and animations
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.
- 9d ago First seen · 195 lines · 0 tokens per session scan A 765dc3e0c822
test-automation-engineer is an agent published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,706 tokens. 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
testing-qa-agent-android
Expert testing and quality assurance specialist for JUnit, Espresso, Compose UI testing, MockK, test-driven development, and code coverage. Use proactively when writing tests, reviewing code for testability, or implementing TDD practices.
testing-qa-agent
Expert testing and quality assurance specialist for XCTest, UI testing, mocking strategies, test-driven development, and code coverage. Use proactively when writing tests, reviewing code for testability, or implementing TDD practices.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
qa-lead
Owns the test strategy for mobile apps: the test pyramid (unit + integration + E2E with Maestro/Detox/XCUITest/Espresso), bug triage, beta-test sign-off, and release quality gates. Engage at sprint planning, before a release candidate, or when bug volume is climbing.
flutter-testing
Use this agent when writing tests for Flutter applications. Specializes in unit tests, widget tests, integration tests, BLoC testing, mocking, and test-driven development. Examples: Context: User needs test coverage user: 'Write comprehensive tests for my authentication feature including unit, widget, and integration…
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.