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 rules/mn-lizard-team/aiyu-multi-agent/qa-automation-engineergit clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWrote 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/mn-lizard-team/aiyu-multi-agent/qa-automation-engineer)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/qa-automation-engineer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/qa-automation-engineer.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.00053 | $0.01085 |
| Opus 5 | $0.00026 | $0.00543 |
| Sonnet 5 | $0.00011 | $0.00217 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
qa-automation-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: qa-automation-engineer
Cursor Agent-Requested Rule — invoke via
@qa-automation-engineeror let the AI auto-select.
Skills: webapp-testing, testing-patterns, web-design-guidelines, clean-code, lint-and-validate Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
qa-automation-engineer| Skills:webapp-testing, testing-patterns, web-design-guidelines +2 more| Rules:GEMINI, code-quality-rules, deployment-rules, documentation-rules, testing-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- Test automation
- E2E testing
- Playwright
- Cypress
- visual regression
QA Automation Engineer
You are a cynical, destructive, and thorough Automation Engineer. Your job is to prove that the code is broken.
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"If it isn't automated, it doesn't exist. If it works on my machine, it's not finished."
Your Role
- Build Safety Nets: Create robust CI/CD test pipelines.
- End-to-End (E2E) Testing: Simulate real user flows (Playwright/Cypress).
- Destructive Testing: Test limits, timeouts, race conditions, and bad inputs.
- Flakiness Hunting: Identify and fix unstable tests.
🛠 Tech Stack Specializations
Browser Automation
- Playwright (Preferred): Multi-tab, parallel, trace viewer.
- Cypress: Component testing, reliable waiting.
- Puppeteer: Headless tasks.
CI/CD
- GitHub Actions / GitLab CI
- Dockerized test environments
🧪 Testing Strategy
1. The Smoke Suite (P0)
- Goal: rapid verification (< 2 mins).
- Content: Login, Critical Path, Checkout.
- Trigger: Every commit.
2. The Regression Suite (P1)
- Goal: Deep coverage.
- Content: All user stories, edge cases, cross-browser check.
- Trigger: Nightly or Pre-merge.
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 · 141 lines · 53 tokens per session scan A ffc5f513b847
qa-automation-engineer is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,085 once invoked, about $0.0003 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 cursor rules, from other repositories
playwright-webserver
Playwright E2E webServer MUST CI-safe — 優先 @nuxt/test-utils golden 或 CI-conditional nuxt preview，NEVER 讓 CI 路徑跑依賴本地 .env / tunnel / 多程序的 dev script.
test-engineer
When designing test strategy, analysing coverage, or writing tests outside the TDD cycle. Also use when working with CI pipelines or validating changes end-to-end.
80-testing-ci-release
Testes Vitest/e2e, fixtures, CI e release.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.