Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/quay/ai-helpersnpx agentmods add skills/quay/ai-helpers/remote-playwrightWrote 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/quay/ai-helpers/remote-playwright)<a href="https://agentmods.dev/skills/quay/ai-helpers/remote-playwright"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/remote-playwright.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.00073 | $0.00489 |
| Opus 5 | $0.00036 | $0.00244 |
| Sonnet 5 | $0.00015 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
remote-playwright 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 2d 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
Remote Playwright Browser
Deploy and connect to a Playwright browser running on an OpenShift cluster.
Arguments
Parse $ARGUMENTS into at most two values before invoking Bash:
- Arg 1: KUBECONFIG path (default:
/tmp/k) - Arg 2: Namespace (default:
playwright)
Step 1: Deploy and Connect
bash .claude/scripts/remote-playwright.sh up "$KUBECONFIG_PATH" "$NAMESPACE"
The script handles everything: version resolution, deployment, port-forwarding, and CLI connection. Wait for the === Ready === output.
Step 2: Verify
npx @playwright/cli goto https://example.com
npx @playwright/cli snapshot
npx @playwright/cli screenshot
Available Commands
npx @playwright/cli goto <url>— navigatenpx @playwright/cli snapshot— accessibility treenpx @playwright/cli screenshot— save PNGnpx @playwright/cli click <ref>— click element by ref from snapshotnpx @playwright/cli fill <ref> <text>— fill inputnpx @playwright/cli video-start/video-stop— record sessionnpx @playwright/cli tab-list/tab-new/tab-select— manage tabs
Teardown
bash .claude/scripts/remote-playwright.sh down "$KUBECONFIG_PATH" "$NAMESPACE"
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.
- 2d ago First seen · 57 lines · 73 tokens per session scan A cd491dde65b9
remote-playwright is a skill published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 73 tokens to every session and 489 once invoked, about $0.0004 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-04.
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.