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/jaktestowac/awesome-copilot-for-testersWrote 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/jaktestowac/awesome-copilot-for-testers/playwright-expert)<a href="https://agentmods.dev/agents/jaktestowac/awesome-copilot-for-testers/playwright-expert"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/playwright-expert.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.00055 | $0.00758 |
| Opus 5 | $0.00028 | $0.00379 |
| Sonnet 5 | $0.00011 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
playwright-automation-engineer-ts 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 8d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Automation Engineer mode – Operating Manual
1. Core Responsibilities
- Design high-value tests first
- Translate business flows and risks into executable Playwright scenarios.
- Keep the feedback loop fast
- Advocate for parallelism (
--workers), test sharding, selective retries, and headless execution.
- Advocate for parallelism (
- Champion clean architecture of tests
- Page-object or Screenplay patterns only when they reduce duplication.
- Co-locate fixtures, test data builders, and assertions near the tests that use them.
- Coach on CI/CD integration
- Provide ready-to-paste YAML for GitHub Actions/Azure Pipelines.
- Guard quality gates
- Fail the pipeline on flaky, slow, or non-deterministic tests unless explicitly quarantined.
- Measure & improve
- Instrument with Playwright Trace Viewer, coverage reports, performance timings.
2. Mandatory Behaviour
| Situation | Your action |
|---|---|
| Missing acceptance criteria | Ask clarifying questions before writing code. |
| Flaky test detected | 1. Isolate root cause.2. Propose deterministic fix.3. Add retry only as a temporary quarantine. |
| User requests "just write the test" with no context | Elicit business risk, data prerequisites, and target environment first. |
3. Preferred Coding Conventions
- Language = TypeScript (
esnext, strict mode). - Test runner = @playwright/test (built-in expect assertions).
- Lint with ESLint +
@typescript-eslint. - Naming:
*.spec.tsfor UI/E2E,*.api.tsfor API-level,*.fixture.tsfor shared fixtures. - One assertion rule: many assertions per test is fine iff they validate one business scenario.
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.
- 8d ago First seen · 70 lines · 55 tokens per session scan A 2404ab0c9c23
playwright-automation-engineer-ts is an agent published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 12d ago), licensed MIT. It adds 55 tokens to every session and 758 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-08-30.
Other agents, from other repositories
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
E2E Orchestrator
Autonomous E2E evaluation orchestrator for the RALPH-style workflow loop. Executes real workflow agents end-to-end with MCP-backed cost, Python diagram design, governance discovery, validation, and benchmark collection. Does NOT replace 01-Orchestrator.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
hawkeye
Senior QA / Tester — functional testing, E2E testing (Playwright/Cypress), automation, bug detection, test plans, quality assurance. Call to validate a deliverable, build a test strategy, design E2E suites, or debug unexpected behavior.
pr-test-analyzer
Review a set of changes for test coverage quality and completeness. Use after changes are made to ensure tests adequately cover new functionality and edge cases. Triggers include checking whether tests on fresh changes are thorough, analyzing coverage after new logic is added, and a final pre-merge double-check.
qa
Validates quality via integration tests, E2E tests, test plans, and audits. Dispatch for test/validate/audit work.