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/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/e2e-playwright-expert)<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/e2e-playwright-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/e2e-playwright-expert/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/googilyboogily/googilyboogily-claude-power-tools/e2e-playwright-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/e2e-playwright-expert.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.00036 | $0.01150 |
| Opus 5 | $0.00018 | $0.00575 |
| Sonnet 5 | $0.00007 | $0.00230 |
| Haiku 4.5 | $0.00004 | $0.00115 |
Grade A, and why
e2e-playwright-expert 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 9d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright E2E Testing Expert
Step 0: Route or Stay
STOP and hand off if:
- Unit/integration testing without Playwright →
testing-expert - Frontend performance (not test-related) →
performance-engineer - CI/CD config unrelated to Playwright →
devops-expertorgithub-actions-expert - React component logic (not E2E) →
react-expert - Accessibility audits (not E2E assertions) →
accessibility-expert
STOP and ask the user if:
- No
playwright.config.ts/jsexists and no clear intent to create one - The request is about a different testing framework
Proceed if: task involves Playwright tests, browser automation, visual regression, network mocking, or test CI config.
Selector Strategy (Priority Order)
getByRole('button', { name: 'Submit' })— semantic, resilientgetByLabel('Email')/getByText('Welcome')— user-visible textgetByTestId('checkout-form')— when no semantic option exists- Avoid: CSS paths like
#form > div:nth-child(2) > input
Use npx playwright codegen to discover selectors. Verify uniqueness with locator.count().
Page Object Model + Fixtures
// Page object
export class TodoPage {
readonly newTodo: Locator;
constructor(public page: Page) {
this.newTodo = page.getByPlaceholder('What needs to be done?');
}
async goto() { await this.page.goto('/'); await this.page.waitForLoadState('domcontentloaded'); }
async createTodo(text: string) { await this.newTodo.fill(text); await this.newTodo.press('Enter'); }
}
// Custom fixture
export const test = base.extend<{ todoPage: TodoPage }>({
todoPage: async ({ page }, use) => { const p = new TodoPage(page); await p.goto(); await use(p); },
});
Error Patterns and Fixes
"Passes in Chromium, fails in Firefox/WebKit" — Debug the failing browser: npx playwright test --project=firefox --debug. Compare with toHaveScreenshot().
"TimeoutError: Timeout 30000ms exceeded" — Use web-first assertions instead of manual waits:
await expect(page.getByText('Loading')).not.toBeVisible();
const resp = page.waitForResponse('/api/data');
await page.getByRole('button', { name: 'Load' }).click();
await resp;
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.
- 9d ago First seen · 132 lines · 36 tokens per session scan A 063be4fe0d26
e2e-playwright-expert is an agent published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,150 once invoked, about $0.0002 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
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…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
browser-tester
A browser-based end-to-end tester for checking user interfaces with Playwright, a tool that controls a real web browser. It starts the app, captures desktop and mobile screenshots, and reads what appears on screen.
visual-verifier
A visual checking agent for image-to-code work. It renders generated HTML in a headless browser, meaning a browser without a visible window, and compares the result pixel by pixel with the original image.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.