Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testersnpx agentmods add agents/jaktestowac/awesome-copilot-for-testers/playwright-expert-detailedWrote 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-detailed)<a href="https://agentmods.dev/agents/jaktestowac/awesome-copilot-for-testers/playwright-expert-detailed"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/playwright-expert-detailed/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/jaktestowac/awesome-copilot-for-testers/playwright-expert-detailed"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/playwright-expert-detailed.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.00054 | $0.03169 |
| Opus 5 | $0.00027 | $0.01584 |
| Sonnet 5 | $0.00011 | $0.00634 |
| Haiku 4.5 | $0.00005 | $0.00317 |
Grade A, and why
playwright-automation-engineer-ts-detailed 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 10d 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 — 355 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.
- 10d ago First seen · 355 lines · 54 tokens per session scan A 399f164caf6c
playwright-automation-engineer-ts-detailed is an agent published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 14d ago), licensed MIT. It adds 54 tokens to every session and 3,169 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
hcc-frontend-iqe-to-playwright-converter
Use this agent to convert IQE/Selenium tests to Playwright TypeScript. This agent implements proper Red Hat SSO authentication (global or isolated), converts fixtures and page objects, modernizes selectors and wait patterns, uses symbolic timeout constants, handles parametrized tests, and organizes converted files by…
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
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.
integ-test-runner
Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issuetype, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.
test-engineer
.NET/C# QA engineer specialized in test strategy, test writing, and coverage analysis — xUnit v3 (or v2) or MSTest with native Assert.X, WebApplicationFactory, Testcontainers, Microsoft.Playwright, and Avalonia.Headless. Use for designing test suites, writing tests for existing code, or evaluating test quality.
Typescript Pro
Expert TypeScript developer specializing in advanced type system usage, full-stack development, and build optimization. Masters type-safe patterns for both frontend and backend with emphasis on developer experience and runtime safety.