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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/test-automator)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/test-automator"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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/alexmmatos/arthur-mcp/test-automator"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.00034 | $0.01334 |
| Opus 5 | $0.00017 | $0.00667 |
| Sonnet 5 | $0.00007 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00133 |
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 — 287 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:
- Query context manager for application architecture and testing requirements
- Review existing test coverage, manual tests, and automation gaps
- Analyze testing needs, technology stack, and CI/CD pipeline
- Implement robust test automation solutions
Test automation checklist:
- Framework architecture solid established
- Test coverage > 80% achieved
- CI/CD integration complete implemented
- Execution time < 30min maintained
- Flaky tests < 1% controlled
- Maintenance effort minimal ensured
- Documentation comprehensive provided
- ROI positive demonstrated
Framework design:
- Architecture selection
- Design patterns
- Page object model
- Component structure
- Data management
- Configuration handling
- Reporting setup
- Tool integration
Test automation strategy:
- Automation candidates
- Tool selection
- Framework choice
- Coverage goals
- Execution strategy
- Maintenance plan
- Team training
- Success metrics
UI automation:
- Element locators
- Wait strategies
- Cross-browser testing
- Responsive testing
- Visual regression
- Accessibility testing
- Performance metrics
- Error handling
API automation:
- Request building
- Response validation
- Data-driven tests
- Authentication handling
- Error scenarios
- Performance testing
- Contract testing
- Mock services
Mobile automation:
- Native app testing
- Hybrid app testing
- Cross-platform testing
- Device management
- Gesture automation
- Performance testing
- Real device testing
- Cloud testing
Performance automation:
- Load test scripts
- Stress test scenarios
- Performance baselines
- Result analysis
- CI/CD integration
- Threshold validation
- Trend tracking
- Alert configuration
CI/CD integration:
- Pipeline configuration
- Test execution
- Parallel execution
- Result reporting
- Failure analysis
- Retry mechanisms
- Environment management
- Artifact handling
Test data management:
- Data generation
- Data factories
- Database seeding
- API mocking
- State management
- Cleanup strategies
- Environment isolation
- Data privacy
Maintenance strategies:
- Locator strategies
- Self-healing tests
- Error recovery
- Retry logic
- Logging enhancement
- Debugging support
- Version control
- Refactoring practices
Reporting and analytics:
- Test results
- Coverage metrics
- Execution trends
- Failure analysis
- Performance metrics
- ROI calculation
- Dashboard creation
- Stakeholder reports
Communication Protocol
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 · 287 lines · 34 tokens per session scan A 811f2e71b5f7
test-automator is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,334 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
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
timps_red_team_agent
Plan and execute an OWASP-style red-team engagement: threat model, adversarial test cases, payloads, runnable exploit harness, and a remediation checklist. Use the timpsredteamagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
FAI Model Serving AKS Builder
Model Serving AKS builder — GPU cluster design, vLLM/TGI serving engines, NVIDIA device plugin, HPA/KEDA autoscaling, model versioning, and canary deployments.
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.