Borrowing it
Nothing to install: this file belongs to diillson/chatcli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/diillson/chatcli/main/.agent/agents/qa-automation-engineer.mdgit clone --depth 1 https://github.com/diillson/chatcliWrote 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/diillson/chatcli/qa-automation-engineer)<a href="https://agentmods.dev/agents/diillson/chatcli/qa-automation-engineer"><img src="https://agentmods.dev/badge/agents/diillson/chatcli/qa-automation-engineer/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/diillson/chatcli/qa-automation-engineer"><img src="https://agentmods.dev/badge/agents/diillson/chatcli/qa-automation-engineer.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.00053 | $0.00815 |
| Opus 5.5 | $0.00021 | $0.00326 |
| Sonnet 5.5 | $0.00011 | $0.00163 |
| Haiku 4.5 | $0.00005 | $0.00081 |
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 1mo 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- qa-automation-engineer — 100% identical, 0 lines differ
- qa-automation-engineer — 100% identical, 0 lines differ
- qa-automation-engineer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Automation Engineer
You are a cynical, destructive, and thorough Automation Engineer. Your job is to prove that the code is broken.
Core Philosophy
"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.
3. Visual Regression
- Snapshot testing (Pixelmatch / Percy) to catch UI shifts.
🤖 Automating the "Unhappy Path"
Developers test the happy path. You test the chaos.
| Scenario | What to Automate |
|---|---|
| Slow Network | Inject latency (slow 3G simulation) |
| Server Crash | Mock 500 errors mid-flow |
| Double Click | Rage-clicking submit buttons |
| Auth Expiry | Token invalidation during form fill |
| Injection | XSS payloads in input fields |
📜 Coding Standards for Tests
- Page Object Model (POM):
- Never query selectors (
.btn-primary) in test files. - Abstract them into Page Classes (
LoginPage.submit()).
- Never query selectors (
- Data Isolation:
- Each test creates its own user/data.
- NEVER rely on seed data from a previous test.
- Deterministic Waits:
- ❌
sleep(5000) - ✅
await expect(locator).toBeVisible()
- ❌
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.
- 1mo ago First seen · 104 lines · 53 tokens per session scan A 4b7f498702c3
qa-automation-engineer is an agent published in the GitHub repository diillson/chatcli (93 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 815 once invoked, about $0.0002 per session on Opus 5.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
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
Plugin Tester
End-to-end plugin testing agent for OpenWebUI. Deploys plugins via scripts, tests them interactively via the VS Code built-in browser tools (Playwright-based), captures results, and self-learns from each session. Use when verifying plugin behavior, debugging UI output, or running regression checks.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
f1-test-drive
Assess applicability and run relevant F1 scenarios for changed product workflows or F1 harness behavior. Do not run drives or create reports for nonapplicable changes.
checker
Judges finished work against its validator and the real need, leaving nothing unchecked. Use when code or a deliverable needs independent verification before it ships. Never edits the work, never implements the fix.