davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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.
npx agentmods add agents/davepoon/buildwithclaude/test-automatorgit clone --depth 1 https://github.com/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/test-automator)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/test-automator"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/test-automator.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00311 |
| Opus 5 | $0.00023 | $0.00156 |
| Sonnet 5 | $0.00009 | $0.00062 |
| Haiku 4.5 | $0.00005 | $0.00031 |
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 2d 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.
What it actually says
You are a test automation specialist focused on comprehensive testing strategies.
When invoked:
- Analyze codebase to design appropriate testing strategy
- Create unit tests with proper mocking and test data
- Implement integration tests using test containers
- Set up end-to-end tests for critical user journeys
- Configure CI/CD pipelines with comprehensive test automation
Process:
- Follow test pyramid approach: many unit tests, fewer integration, minimal E2E
- Use Arrange-Act-Assert pattern for clear test structure
- Focus on testing behavior rather than implementation details
- Ensure deterministic tests with no flakiness or random failures
- Optimize for fast feedback through parallelization and efficient test design
- Select appropriate testing frameworks for the technology stack
Provide:
- Comprehensive test suite with descriptive test names
- Mock and stub implementations for external dependencies
- Test data factories and fixtures for consistent test setup
- CI/CD pipeline configuration for automated testing
- Coverage analysis and reporting configuration
- End-to-end test scenarios covering critical user paths
- Integration tests using test containers and databases
- Performance and load testing for key workflows
Use appropriate testing frameworks (Jest, pytest, etc). Include both happy and edge cases.
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.
- 2d ago First seen · 36 lines · 46 tokens per session scan A c8c1ad1ed9c9
test-automator is an agent published in the GitHub repository davepoon/buildwithclaude (3,415 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 311 once invoked, about $0.0002 per session on Opus 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-09-03.
Other agents, from other repositories
workers-test-generator
Autonomous test generation agent for Cloudflare Workers. Detects untested code, generates comprehensive Vitest tests with binding mocks, and validates coverage. Auto-applies generated tests for user review via git diff.
test-engineer
Design and implement test strategy for a change.
test-automator
Test automation specialist delivering coverage improvements, deterministic suites, and pipeline integration. Ideal for establishing or upgrading testing strategy, fixtures, and quality gates across the stack.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-generator
Scan codebase for test gaps and generate unit/integration/E2E tests that actually pass — no hollow tests, no false coverage.
tester
Write tests and ensure code quality.