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 skills/joinwell52-ai/codeflowmu-open/browser-playwright-checknpx skills add joinwell52-AI/CodeFlowMu-open --skill browser-playwright-checkgit clone --depth 1 https://github.com/joinwell52-AI/CodeFlowMu-openWrote 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/skills/joinwell52-ai/codeflowmu-open/browser-playwright-check)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/browser-playwright-check"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/browser-playwright-check.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.00045 | $0.00462 |
| Opus 5 | $0.00023 | $0.00231 |
| Sonnet 5 | $0.00009 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
browser-playwright-check 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 5d 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.
What it actually says
Browser Playwright Check
When to use
Use when the task requires browser-visible evidence or interactive web verification.
Typical triggers:
- Open a local HTML file or dev-server URL in a browser.
- Click through UI, fill a form, test navigation, or inspect page state.
- Capture screenshots for evidence.
- Verify responsive layouts across desktop and mobile viewports.
- Check canvas, media, animation, or visual nonblank rendering.
- Diagnose Panel or web app behavior that cannot be proven by static code reading.
Rules
- Prefer an existing project test command if it already uses Playwright.
- If no test exists, write the smallest ad hoc Playwright check needed for evidence.
- Use stable selectors where available; otherwise use visible text, roles, or narrow DOM queries.
- Verify behavior, not only file existence.
- Capture evidence: command output, screenshot paths, viewport sizes, URL, and pass/fail notes.
- Keep browser automation scoped to local/dev URLs or explicit user-provided URLs.
- Do not require network access unless the task explicitly depends on a remote page.
- Do not hide flaky or unverified criteria in the final report.
Required output
When reporting, include:
- URL or local file opened.
- Viewports tested.
- Interactions performed.
- Evidence paths for screenshots or traces when captured.
- Any untested or flaky criteria.
Forbidden actions
- Do not use Playwright as a substitute for code review when source inspection is required.
- Do not perform destructive UI actions unless explicitly authorized.
- Do not log secrets, session tokens, cookies, or private form data.
- Do not mark a visual/UI task done without at least one browser-visible verification when a browser can run locally.
Minimal example
Check: open http://127.0.0.1:5173, click "Submit", verify success toast
Viewport: 1280x720 and 390x844
Evidence: screenshots/playwright-submit-desktop.png
Result: 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.
- 5d ago First seen · 57 lines · 45 tokens per session scan A ad08fd0f4115
browser-playwright-check is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 11d ago), licensed MIT. It adds 45 tokens to every session and 462 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-08-31.
Other skills, from other repositories
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
qa/e2e-playwright
Playwright E2E 测试完整方法论，涵盖项目初始化、Page Object Model、认证复用、API Mock、视觉回归、多浏览器测试、CI 集成和调试技巧.
Console Error Hunter
Systematically detect, capture, and categorize browser console errors, warnings, and unhandled exceptions during automated test execution.
playwright-e2e
Comprehensive end-to-end testing skill using Playwright for web applications, covering page objects, selectors, assertions, waits, fixtures, and test organization.