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 omnigentx/jarvis --skill playwright-skillgit clone --depth 1 https://github.com/omnigentx/jarvisWrote 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/omnigentx/jarvis/playwright-skill)<a href="https://agentmods.dev/skills/omnigentx/jarvis/playwright-skill"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/playwright-skill.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.00873 |
| Opus 5 | $0.00026 | $0.00436 |
| Sonnet 5 | $0.00011 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
playwright-skill 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 8d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Browser Automation
Write custom Playwright scripts, execute via universal executor. Scripts go to /tmp (works on macOS/Linux/Docker — all Jarvis target environments). Never write to skill or project directory.
Setup (First Time Only)
cd $SKILL_DIR && npm run setup
Critical Workflow
-
Detect dev servers (for localhost testing):
cd $SKILL_DIR && node -e "require('./lib/helpers').detectDevServers().then(s => console.log(JSON.stringify(s)))"- 1 server → use it automatically
- Multiple → ask user which one
- None → ask for URL or help start server
-
Write script to /tmp — NEVER to skill directory or project:
// /tmp/playwright-test-xxx.js const { chromium } = require('playwright'); const TARGET_URL = 'http://localhost:3001'; // Auto-detected (async () => { const browser = await chromium.launch({ headless: false }); const page = await browser.newPage(); await page.goto(TARGET_URL); console.log('Page loaded:', await page.title()); await page.screenshot({ path: '/tmp/screenshot.png', fullPage: true }); await browser.close(); })(); -
Execute from skill directory:
cd $SKILL_DIR && node run.js /tmp/playwright-test-xxx.js
Defaults
| Setting | Default | Override |
|---|---|---|
| Browser | Chromium | headless: false by default |
| Viewport | 1280×720 | page.setViewportSize(...) |
| Scripts | /tmp/playwright-test-*.js |
Never write to project dir |
| URLs | Auto-detected via detectDevServers() |
TARGET_URL constant at top |
Anti-Patterns (from browser-automation best practices)
| ❌ Don't | ✅ Do |
|---|---|
waitForTimeout(5000) |
waitForSelector('.element') or waitForURL(...) |
page.locator('.btn-primary') |
page.getByRole('button', { name: 'Submit' }) |
| Single browser context for all tests | Fresh context per test |
| CSS/XPath first | User-facing locators: text=, role=, data-testid= |
What ships with it
4 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.
- 8d ago First seen · 105 lines · 53 tokens per session scan A 164319bf261c
playwright-skill is a skill published in the GitHub repository omnigentx/jarvis (37 stars, last pushed 11d ago), licensed MIT. It adds 53 tokens to every session and 873 once invoked, about $0.0003 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.
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…
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.