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/bugrabilge/bilge-development-kit/qa-automation-engineergit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWhat 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 | $0.00053 | $0.00815 |
| Opus 5 | $0.00026 | $0.00407 |
| Sonnet 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 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.
This is a copy
100% identical to qa-automation-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 2d ago First seen · 104 lines · 53 tokens per session scan A 4b7f498702c3
qa-automation-engineer is an agent published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 815 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to qa-automation-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
testing-automation-engineer
Testing automation: Vitest, Playwright, E2E, coverage enforcement, CI/CD integration.
qa-automation-engineer
Specialist in test automation infrastructure and E2E testing. Focuses on Playwright, Cypress, CI pipelines, and breaking the system. Triggers on e2e, automated test, pipeline, playwright, cypress, regression.
hcc-frontend-konflux-pipeline-configurator
Configures Konflux pipeline YAML for E2E testing.
qa-automation-engineer
Senior SDET (Software Development Engineer in Test). Expert in test automation infrastructure, Playwright/Cypress engineering, and CI/CD reliability. Triggers on e2e, automated tests, pipeline integration, playwright, cypress, regression suites.
ci-architect
Specialized agent for designing comprehensive CI/CD strategies with GitHub Actions, integration testing, and end-to-end test orchestration. Use when planning CI pipelines, implementing workflows, debugging CI issues, or designing test strategies.
qa-automation-engineer
测试自动化基础设施与 E2E 测试专家。专注于 Playwright、Cypress、CI（持续集成）流水线以及打破系统。触发关键词：e2e, automated test, pipeline, playwright, cypress, regression。.