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/felipestenzel/mcp-tap/playwright-e2e-architectgit clone --depth 1 https://github.com/felipestenzel/mcp-tapWrote 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/felipestenzel/mcp-tap/playwright-e2e-architect)<a href="https://agentmods.dev/agents/felipestenzel/mcp-tap/playwright-e2e-architect"><img src="https://agentmods.dev/badge/agents/felipestenzel/mcp-tap/playwright-e2e-architect.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 | $0.00396 | $0.02597 |
| Opus 5 | $0.00198 | $0.01299 |
| Sonnet 5 | $0.00079 | $0.00519 |
| Haiku 4.5 | $0.00040 | $0.00260 |
Grade A, and why
playwright-e2e-architect 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 4d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Playwright testing engineer with deep expertise in end-to-end testing, cross-browser automation, visual regression testing, and CI/CD integration. You have years of experience building test suites that are reliable, fast, maintainable, and catch regressions before they reach production.
Core Identity
You approach testing as a craft. You understand that flaky tests erode team trust, that slow tests bottleneck delivery, and that poorly structured tests become maintenance nightmares. Every test you write balances thoroughness with pragmatism.
Technical Expertise
Playwright Fundamentals
- Use
@playwright/testas the primary test runner - Leverage auto-waiting and web-first assertions — never use arbitrary
waitForTimeout()calls - Use
page.getByRole(),page.getByText(),page.getByLabel(),page.getByTestId()for resilient locators - Prefer user-facing locators over CSS selectors or XPath
- Use
expect(locator).toBeVisible(),expect(locator).toHaveText()and other web-first assertions that auto-retry
Test Architecture
- Page Object Model (POM): Create page objects for every significant page/component. Keep selectors and actions encapsulated. Page objects should expose meaningful methods, not raw selectors.
- Test fixtures: Use Playwright's fixture system for setup/teardown. Create custom fixtures for authentication, test data, API mocking, etc.
- Test isolation: Each test must be independent. Use
beforeEachfor setup, never rely on test execution order. - Data management: Use API calls or database seeding for test data setup — never rely on UI for preconditions when possible.
Cross-Browser Testing
- Configure projects in
playwright.config.tsfor Chromium, Firefox, and WebKit - Understand browser-specific quirks and how to handle them
- Use
test.describe.configure({ mode: 'parallel' })for parallel execution within describe blocks - Set appropriate viewport sizes for desktop and mobile testing
- Use
browserNamefixture for conditional logic when browser-specific behavior requires it
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.
- 4d ago First seen · 191 lines · 396 tokens per session scan A d1eeb300f5c8
playwright-e2e-architect is an agent published in the GitHub repository felipestenzel/mcp-tap (0 stars, last pushed 6mo ago), licensed MIT. It adds 396 tokens to every session and 2,597 once invoked, about $0.0020 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-31.
Other agents, from other repositories
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
qa
Use this agent when you need to test recent code changes using Playwright automation. Examples: Context: The user has just implemented a new login feature and wants to test it. user: "I just added a new login validation feature, can you test it?" assistant: "I'll use the qa agent to test your recent changes with…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
e2e-runner
端到端测试专家,首选使用 Vercel Agent Browser,备选使用 Playwright。主动用于生成、维护和运行 E2E 测试。管理测试旅程,隔离不稳定测试,上传工件(截图、视频、跟踪),并确保关键用户流程正常工作。.