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 Arnosdeus/agent-toolkit --skill playwrightgit clone --depth 1 https://github.com/Arnosdeus/agent-toolkitWrote 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/arnosdeus/agent-toolkit/playwright)<a href="https://agentmods.dev/skills/arnosdeus/agent-toolkit/playwright"><img src="https://agentmods.dev/badge/skills/arnosdeus/agent-toolkit/playwright/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/arnosdeus/agent-toolkit/playwright"><img src="https://agentmods.dev/badge/skills/arnosdeus/agent-toolkit/playwright.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.00029 | $0.00197 |
| Opus 5.5 | $0.00012 | $0.00079 |
| Sonnet 5.5 | $0.00006 | $0.00039 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
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 1mo 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
Playwright
Use the project's existing Playwright setup when present. Start the application with its documented command, wait for its actual readiness signal, and use headless Chromium unless a headed run is needed for diagnosis.
Cover meaningful flows: navigation and deep links, keyboard access, forms and validation, loading/empty/error states, authentication boundaries, and responsive viewports. Capture screenshots at stable points. Listen for page console errors, uncaught exceptions, failed requests, and unexpected redirects. Prefer stable roles, labels, and user-visible text over brittle selectors. Clean up test data, avoid secrets, and report browser/version and known limitations.
Typical commands: npx playwright test, npx playwright test --headed, and
npx playwright install chromium. Do not install unnecessary browsers.
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.
- 1mo ago First seen · 21 lines · 29 tokens per session scan A fbd3f02eb219
playwright is a skill published in the GitHub repository Arnosdeus/agent-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 197 once invoked, about $0.0001 per session on Opus 5.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
ui-control
Verify graphical browser, desktop, or Electron behavior through the actual interface. Use when screenshot, accessibility, console, network, trace, or browser-driven evidence is required; not for terminal-hosted interfaces, which belong to cli-control.
playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes reusable test scripts, and supports screenshots, responsive checks, UX validation, login flows, link checks, and arbitrary browser automation. Use when the user wants to test a website, automate browser interactions, validate web…
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.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
browser-automation
Playwright browser automation via MCP. Covers E2E testing, UI review, web scraping, screenshot capture, and general browser interaction. MCP-first — CLI is fallback only.
playwright
Playwright end-to-end testing best practices for web applications, covering test design, locator strategies, and assertion patterns.