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 skills add tan-yong-sheng/ai-vision-mcp --skill playwright-cli-automationgit clone --depth 1 https://github.com/tan-yong-sheng/ai-vision-mcpWrote 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/tan-yong-sheng/ai-vision-mcp/playwright-cli-automation)<a href="https://agentmods.dev/skills/tan-yong-sheng/ai-vision-mcp/playwright-cli-automation"><img src="https://agentmods.dev/badge/skills/tan-yong-sheng/ai-vision-mcp/playwright-cli-automation/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/skills/tan-yong-sheng/ai-vision-mcp/playwright-cli-automation"><img src="https://agentmods.dev/badge/skills/tan-yong-sheng/ai-vision-mcp/playwright-cli-automation.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.00030 | $0.02914 |
| Opus 5 | $0.00015 | $0.01457 |
| Sonnet 5 | $0.00006 | $0.00583 |
| Haiku 4.5 | $0.00003 | $0.00291 |
Grade A, and why
playwright-cli-automation 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 12d 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 — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Screenshot Capture with CLI
Capture full-page screenshots, navigate authentication flows, run Lighthouse audits, and test responsive design using playwright-cli commands. No code writing required.
When to Use
- Capture screenshots for accessibility audits (feed to
/design-eval:audit-accessibility) - Navigate login flows and capture authenticated pages
- Run Lighthouse accessibility/performance reports
- Test responsive design across mobile, tablet, desktop
- Generate before/after comparisons at specific viewports
- Automate screenshot capture without writing Playwright code
Key Features
- CLI-based — No JavaScript code to write or maintain
- Full-page captures — Entire page content, not just viewport
- Lighthouse integration — Built-in accessibility and performance audits
- Authentication support — Fill forms, submit, navigate authenticated flows
- Fixed viewports — Consistent sizes across runs (mobile, tablet, desktop)
- Snapshot management — Auto-generated snapshots for debugging
- Session persistence — Save/load browser state for multi-step flows
Quick Start
Basic Capture (Desktop)
# Create .playwright-cli directory if it doesn't exist
mkdir -p .playwright-cli
# Open browser and navigate
playwright-cli open http://localhost:8787
# Take screenshot (saves to .playwright-cli/page-*.png)
playwright-cli screenshot --filename=.playwright-cli/login-page.png
# Close browser
playwright-cli close
Capture with Lighthouse Audit
# Create .playwright-cli directory if it doesn't exist
mkdir -p .playwright-cli
# Open browser
playwright-cli open http://localhost:8787
# Get page snapshot for reference
playwright-cli snapshot --filename=.playwright-cli/before-audit.yaml
# Run Lighthouse audit (accessibility + performance)
playwright-cli run-code "async page => {
const result = await page.evaluate(() => {
return {
url: window.location.href,
title: document.title,
accessibility: 'audit-required'
};
});
return result;
}"
# Take screenshot
playwright-cli screenshot --filename=.playwright-cli/login-lighthouse.png
# Close
playwright-cli close
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 457 lines · 30 tokens per session scan A 7f9fa1961407
playwright-cli-automation is a skill published in the GitHub repository tan-yong-sheng/ai-vision-mcp (78 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 2,914 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-30.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…