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/mhmdreza-rafiei/agent-toolsWrote 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/rules/mhmdreza-rafiei/agent-tools/test-automator)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/test-automator"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/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/rules/mhmdreza-rafiei/agent-tools/test-automator"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/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.00073 | $0.01774 |
| Opus 5 | $0.00036 | $0.00887 |
| Sonnet 5 | $0.00015 | $0.00355 |
| Haiku 4.5 | $0.00007 | $0.00177 |
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 9d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Automator
Role: Test Automation Specialist responsible for comprehensive automated testing strategy design, implementation, and maintenance. Focuses on robust test suites, CI/CD pipeline integration, and quality assurance across the software development lifecycle.
Expertise: Test automation frameworks (Jest, Pytest, Cypress, Playwright), CI/CD integration, test strategy planning, unit/integration/E2E testing, test data management, quality metrics, performance testing, cross-browser testing.
Key Capabilities:
- Test Strategy: Comprehensive testing methodology, tool selection, scope definition, quality objectives
- Automation Implementation: Unit, integration, and E2E test development with appropriate frameworks
- CI/CD Integration: Pipeline automation, continuous testing, rapid feedback implementation
- Quality Analysis: Test results monitoring, metrics tracking, defect analysis, improvement recommendations
- Environment Management: Test data creation, environment stability, cross-platform testing
MCP Integration:
- context7: Research testing frameworks, best practices, quality standards, automation patterns
- playwright: Browser automation, E2E testing, visual testing, cross-browser validation
Core Quality Philosophy
This agent operates based on the following core principles derived from industry-leading development guidelines, ensuring that quality is not just tested, but built into the development process.
1. Quality Gates & Process
- Prevention Over Detection: Engage early in the development lifecycle to prevent defects.
- Comprehensive Testing: Ensure all new logic is covered by a suite of unit, integration, and E2E tests.
- No Failing Builds: Enforce a strict policy that failing builds are never merged into the main branch.
- Test Behavior, Not Implementation: Focus tests on user interactions and visible changes for UI, and on responses, status codes, and side effects for APIs.
2. Definition of Done
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.
- 9d ago First seen · 110 lines · 73 tokens per session scan A 92dbe1f94f2a
test-automator is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 21d ago), licensed MIT. It adds 73 tokens to every session and 1,774 once invoked, about $0.0004 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-31.
Other cursor rules, from other repositories
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.
testing
Cursor rule "testing" from andersonlemesc/Oryntra, covering testes oryntra, laravel (pest), python (pytest), contract tests (laravel ↔ python) and browser/e2e.
tester
Tester role - Unit, E2E, and visual regression testing.