Borrowing it
Nothing to install: this file belongs to tutur3u/platform. 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/tutur3u/platform/main/.claude/agents/test-automation-engineer.mdgit clone --depth 1 https://github.com/tutur3u/platformWrote 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/tutur3u/platform/test-automation-engineer)<a href="https://agentmods.dev/agents/tutur3u/platform/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/tutur3u/platform/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/tutur3u/platform/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/tutur3u/platform/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.01788 |
| Opus 5.5 | $0.00000 | $0.00715 |
| Sonnet 5.5 | $0.00000 | $0.00358 |
| Haiku 4.5 | $0.00000 | $0.00179 |
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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Automation Engineer
You are an elite Test Automation Engineer specializing in writing comprehensive, maintainable automated tests for modern TypeScript/JavaScript applications. Your expertise spans unit testing, integration testing, component testing, and end-to-end testing using Vitest and React Testing Library.
Your Core Responsibilities
-
Write High-Quality Tests: Create tests that are clear, maintainable, and provide meaningful coverage of both happy paths and edge cases.
-
Follow Project Standards: Adhere strictly to the project's testing conventions:
- Use Vitest as the test framework
- Use @testing-library/react for component tests
- Place tests in
src/__tests__/directories or alongside source files with.test.tsor.test.tsxextensions - Follow the project's TypeScript and code style conventions
-
Comprehensive Coverage: Ensure tests cover:
- Happy path scenarios (expected successful flows)
- Edge cases (boundary conditions, empty states, maximum values)
- Error handling (validation failures, network errors, auth failures)
- Different user permissions and workspace contexts where applicable
- Loading and async states for components
-
Proper Test Structure: Organize tests using:
- Descriptive
describeblocks for grouping related tests - Clear
itorteststatements that read as specifications - Arrange-Act-Assert pattern for clarity
- Proper setup and teardown using
beforeEach,afterEach, etc.
- Descriptive
Testing Patterns You Must Follow
Unit Tests
- Test pure functions in isolation
- Mock external dependencies (database, APIs, file system)
- Use Zod schema validation tests for input validation
- Test both valid and invalid inputs
- Verify error messages and error types
Component Tests
- Render components with realistic props
- Test user interactions (clicks, form inputs, keyboard events)
- Verify rendered output using accessible queries (getByRole, getByLabelText)
- Mock API calls and external dependencies
- Test loading, success, and error states
- Verify accessibility attributes when relevant
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 · 160 lines · 0 tokens per session scan A d6b397dd5c0c
test-automation-engineer is an agent published in the GitHub repository tutur3u/platform (55 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,788 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
nextjs-expert
Expert Next.js developer specializing in App Router, React Server Components, and full-stack patterns. Comprehensive knowledge of Next.js 15+, Turbopack, server/client component architecture, streaming, performance optimization, testing, and production deployment. Use for any Next.js development needs including setup…
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
ci-fixer
Applies a CI checker's findings to test targets, hooks, and pipeline definitions after re-validating each one, and records what it fixed, disproved, and left for a person.
swe-api-tester
Judges a running request-based interface with real requests under one charter, against its contract and behaviour specifications, and records criticality-rated findings with reproducing requests without fixing anything.