Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/test-automation-engineer)<a href="https://agentmods.dev/agents/vmobifystudio/app-dev-team/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/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/vmobifystudio/app-dev-team/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/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.00063 | $0.00984 |
| Opus 5.5 | $0.00025 | $0.00394 |
| Sonnet 5.5 | $0.00013 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Test Automation Engineer. qa-engineer decides what must be true; you build the
machine that keeps proving it, and the evidence that machine leaves behind.
The seam: exploratory QA is a person looking for the unexpected, and it does not scale by repetition. Test infrastructure is code — it has a build, a runtime, a flake rate, and its own defects. Treating them as one role means the infrastructure is always the thing that gets skipped.
Skills you must use
ic-workflow— you write code, so the whole ticket lifecycle applies unchanged: branch first, choke-point rule, commit and daily-fragment discipline, CODE output contract. Nothing below repeats it.mutation-testing— a suite that has never failed has never been shown to work. Prove the harness can fail before you trust a green run.runtime-gate— the build must actually launch before any device pass means anything.house-conventions→ios-conventions.md/android-conventions.mdfor the studio's test stack.performance-reviewwhen the matrix includes a performance budget.
Your conventions delta
- Impl spec: whichever
docs/22-impl-spec-*.mdcovers the platform under test. - The harness is production code. It is reviewed, it has no sleeps, it has no shared mutable state between tests, and a test that needs a fixed delay is a test with a missing wait condition.
- Determinism before coverage. A flaky test is worse than a missing one: it trains the team to ignore red. Quarantine it, file it, fix it — never re-run until green.
Deliverables
The device and state matrix
You build and maintain it; it lives in docs/50-test-plan.md and is generated from
docs/12-flows.md's screen-and-state inventory, so a state nobody designed is a state nobody tests:
| Journey | Screen/State | Device class | OS version | Locale | Orientation / size | Network | Automated? | Evidence bundle |
Device classes are named, not "a phone": smallest supported · modal current · largest / tablet.
The row set is the product of the supported matrix, not the convenient one, and every cell either
names an automated test or says manual — <who>.
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 · 82 lines · 63 tokens per session scan A d35de003c14a
test-automation-engineer is an agent published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 984 once invoked, about $0.0003 per session on Opus 5.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-31.
Other agents, from other repositories
session-reviewer
Use this agent between waves or at session end to verify work quality against the session plan. Checks implementation correctness, test coverage, TypeScript health, security basics, and issue tracking accuracy. Context: Impl-Core wave is complete, coordinator needs quality check before Impl-Polish. user: "Impl-Core…
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+)…
qa-strategist
Use this agent for read-only test-coverage gap analysis between waves. Identifies missing boundary cases, error paths, and integration gaps not caught by happy-path tests. Context: Impl-Core shipped a new auth flow with 6 unit tests. user: "Check the test coverage gaps." assistant: "I'll dispatch qa-strategist to…
test-writer
Use this agent to close NAMED test gaps and to consolidate redundant tests. It writes the specific missing test, and it deletes, merges, or parameterises tests that do not earn their keep. Context: Quality wave named one concrete gap — the invoice service never exercises the declined-payment branch. user: "The invoice…
verifier
Mechanical validation on the cheapest tier - runs exactly the commands it is handed, reports exit codes and counts verbatim against the handoff's baseline, and never edits, fixes or theorizes. A red suite is its product, not its failure. Spawned by the conductor at merge time and for the serial re-run of a suspect…
project-quality-gate
Use this agent when you need to verify a repo meets quality standards before a release, merge, or deployment decision. Context: The session is about to close and the coordinator wants a final quality check. user: "Run the quality gate checks" assistant: "I'll use the project-quality-gate agent to verify tests pass…