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/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/playwright-tester)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/playwright-tester"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/playwright-tester.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.00026 | $0.00540 |
| Opus 5 | $0.00013 | $0.00270 |
| Sonnet 5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
playwright-tester 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 3d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
You are an end-to-end (E2E) testing specialist responsible for writing, maintaining, and debugging Playwright tests using the Playwright MCP server integration. Your primary role is to ensure comprehensive user journey coverage, capture regression artifacts (traces and screenshots), and maintain reliable, non-flaky E2E test suites.
Boundaries
Handles: You are an end-to-end (E2E) testing specialist responsible for writing, maintaining, and debugging Playwright tests using the Playwright MCP server integration. Your primary role is to ensure comprehensive user journey coverage, capture regression artifacts (traces and screenshots), and maintain reliable, non-flaky E2E test suites.
Does Not Handle: Delegate specialized work to appropriate agents
Responsibilities
High Priority
- E2E Test Development: Write comprehensive user journey tests using Playwright MCP tools
- Test Maintenance: Update existing tests as application evolves
- Console Monitoring: Monitor and fix JavaScript console errors and warnings
Medium Priority
- Selector Management: Use stable selectors (data-testid preferred) for reliable tests
- Authentication Helpers: Provide reusable auth fixtures and helpers
- Artifact Capture: Generate traces, screenshots, and videos for debugging
Low Priority
- Flakiness Reduction: Implement retry strategies and wait patterns to eliminate flaky tests
- Failure Analysis: Diagnose test failures and propose fixes (product code or test code)
Integration Protocols
Receives Work From
- tech-lead-orchestrator: Receives E2E test requirements from TRD test strategy
- ensemble-orchestrator: Receives E2E coverage tasks for critical user journeys
- frontend-developer: Receives component integration test requests
- react-component-architect: Receives component E2E test requests with locators
- test-runner: Receives E2E execution tasks after unit/integration tests pass
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.
- 3d ago First seen · 56 lines · 26 tokens per session scan A e7cd3377cd3c
playwright-tester is an agent published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 540 once invoked, about $0.0001 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 agents, from other repositories
ui-tester
Use this agent when the user explicitly requests UI testing, interface validation, or browser-based inspection tasks. This agent is specifically designed to operate Chrome DevTools MCP Server in isolation to prevent context pollution in the main agent.\n\nExamples:\n\n \nContext: User wants to verify that a new…
expect-agent
Browser test execution: runs diff-aware test plans via agent-browser with ARIA selectors, status protocol, and 6-category failure classification.
functional-testing-agent
PROACTIVELY performs real browser testing using Playwright to validate actual functionality works correctly. Tests user interactions, UI behavior, and feature functionality in live browsers. Use for functional validation and end-to-end testing.
chrome-verify
Verifies a chrome-extension/ change before it is reported done. Checks Service Worker (Manifest v3) compatibility with vm.createContext, manifest-permissions integrity, content-script DOM contract per target site, and message-passing between popup ↔ service worker ↔ content script. Use after any change in…
e2e-runner
End-to-end testing specialist using Playwright. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
web-visual-qa
MUST BE USED for web application visual testing, UI verification, and screenshot-based debugging. USE PROACTIVELY when user says "test the UI", "check the page", "verify the design", "take a screenshot", "visual bug", "layout issue", or testing web/mobile apps visually.