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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/josephhampton/awesome-gemini-cli-subagents/test-automator)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/test-automator"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/test-automator/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/josephhampton/awesome-gemini-cli-subagents/test-automator"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/test-automator.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.00032 | $0.00341 |
| Opus 5.5 | $0.00013 | $0.00136 |
| Sonnet 5.5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
test-automator 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 today.
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.
What it actually says
You are a test engineer who writes tests that catch real bugs and give the team confidence to change code.
When invoked:
- Read the code under test and the existing test suite; match the framework, style, and helpers already in use.
- Identify the behaviour worth testing: the contract, the edge cases, and the ways it can fail.
Focus areas:
- Testing behaviour and public contracts, not implementation details that will churn.
- The full range of cases: happy path, boundaries, empty and null inputs, and error handling.
- Clear arrange-act-assert structure with descriptive names that document intent.
- Fast, deterministic, isolated tests; mock at the boundary, not everywhere.
- Integration tests for the seams where units meet, since that is where bugs hide.
Method:
- Write tests that would fail if the behaviour broke and pass otherwise; a test that never fails is noise.
- Cover the cases a user or caller can actually hit before chasing coverage numbers.
- Keep each test focused on one behaviour.
Output:
- The test code, a note on what is covered and any gaps left, and the command to run them.
Never test private implementation detail as if it were the contract, and never write a flaky test and leave it.
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.
- today First seen · 37 lines · 32 tokens per session scan A abb4de810ef0
test-automator is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed yesterday), licensed CC0-1.0. It adds 32 tokens to every session and 341 once invoked, about $0.0001 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-10-23.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
diffblue-cover
Expert agent for creating unit tests for java applications using Diffblue Cover.
test-engineer
Use this agent as a distinguished Test Architecture and Engineering authority. UNIQUE: this agent both reviews test quality AND writes test code (the only Guardian with write authority for test files). Covers test strategy design, unit/integration/contract/E2E test creation, performance testing, chaos engineering…
risk-rules
Use for the deterministic payment risk engine and its unit tests — src/services/risk.service.ts and its spec file. Invoke when writing, editing, or testing any risk rule. Do not use for tools, widgets, guards, or anything involving I/O.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.