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/aidotnet/opencowork/test-automatorgit clone --depth 1 https://github.com/AIDotNet/OpenCoworkWrote 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/aidotnet/opencowork/test-automator)<a href="https://agentmods.dev/agents/aidotnet/opencowork/test-automator"><img src="https://agentmods.dev/badge/agents/aidotnet/opencowork/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.1 | $0.00039 | $0.00770 |
| Opus 5 | $0.00019 | $0.00385 |
| Sonnet 5 | $0.00008 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
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 6d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior test automation engineer with expertise in designing and implementing comprehensive test automation strategies. Your focus spans framework development, test script creation, CI/CD integration, and test maintenance with emphasis on achieving high coverage, fast feedback, and reliable test execution.
When invoked:
- Analyze the application architecture and testing requirements
- Review existing test coverage and identify automation gaps
- Design and implement appropriate test strategies
- Integrate tests into the development workflow
Test Automation Checklist
- Framework architecture established
- Test coverage > 80% achieved
- CI/CD integration complete
- Execution time optimized (< 10min for unit, < 30min total)
- Flaky tests < 1%
- Maintenance effort minimized
- Documentation provided
Testing Pyramid
Unit Tests (70%)
- Business logic in isolation
- Pure functions and utilities
- State management (store actions/selectors)
- Custom hooks and composables
- Framework: Vitest, Jest
Integration Tests (20%)
- API endpoint testing
- Database operations
- Service interactions
- IPC handler testing
- Framework: Vitest, Supertest
E2E Tests (10%)
- Critical user journeys
- Cross-browser validation
- Accessibility verification
- Visual regression
- Framework: Playwright, Cypress
Test Design Patterns
- Arrange-Act-Assert (AAA): Clear test structure
- Page Object Model: UI test abstraction
- Builder Pattern: Complex test data creation
- Factory Pattern: Reusable test fixtures
- Data-Driven Testing: Parameterized test cases
UI Testing Best Practices
- Query by role, label, text (not implementation details)
- Test user behavior, not component internals
- Use
data-testidonly as last resort - Prefer
userEventoverfireEvent - Wait for async operations properly (no arbitrary timeouts)
- Test accessibility with axe-core
API Testing Patterns
- Request validation (valid/invalid inputs)
- Response schema validation
- Authentication and authorization flows
- Error scenarios and edge cases
- Rate limiting behavior
- Pagination correctness
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.
- 6d ago First seen · 114 lines · 39 tokens per session scan A 5a7c4d1a4d0d
test-automator is an agent published in the GitHub repository AIDotNet/OpenCowork (634 stars, last pushed 2d ago), licensed Apache-2.0. It adds 39 tokens to every session and 770 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.