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 thapaliyabikendra/ai-artifacts --skill playwright-integrationgit clone --depth 1 https://github.com/thapaliyabikendra/ai-artifactsWrote 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/thapaliyabikendra/ai-artifacts/playwright-integration)<a href="https://agentmods.dev/skills/thapaliyabikendra/ai-artifacts/playwright-integration"><img src="https://agentmods.dev/badge/skills/thapaliyabikendra/ai-artifacts/playwright-integration/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/thapaliyabikendra/ai-artifacts/playwright-integration"><img src="https://agentmods.dev/badge/skills/thapaliyabikendra/ai-artifacts/playwright-integration.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.00158 | $0.01296 |
| Opus 5 | $0.00079 | $0.00648 |
| Sonnet 5 | $0.00032 | $0.00259 |
| Haiku 4.5 | $0.00016 | $0.00130 |
Grade A, and why
playwright-integration 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 7d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Integration Skill
Dynamic, framework-agnostic Playwright assistant for any web project.
Command
/playwright-integration
What It Does
Auto-detects your web framework and provides tailored Playwright setup:
- Framework Detection: React, Vue, Angular, Svelte, Next.js, Nuxt, Solid, Qwik
- Build Tool Detection: Vite, Webpack, Rspack, Angular CLI, Next.js CLI, Nuxt CLI
- Routing Detection: React Router, Vue Router, Angular Router, file-based routing
- Auth Pattern Detection: OIDC, JWT, NextAuth, session-based, custom
- UI Library Detection: MUI, AntD, Tailwind, Bootstrap, Element Plus, etc.
Pre-Generation Validation Phase (MANDATORY)
Before generating ANY test code, you MUST gather:
- Environment: dev / staging / prod
- Base URL: Full application URL (e.g.,
http://localhost:4200,https://app-dev.example.com) - Credentials: Valid username/password (or API keys) for authentication tests
- ASK: "Please provide a valid username and password for the [ENVIRONMENT] environment"
- NEVER use placeholder values like '[email protected]' or 'password123'
- Auth bypass: Does your backend provide test auth endpoints (e.g.,
/api/auth/test-login)? - Test data: Are seeded test users/data available?
Validation Checklist (complete before code generation):
- Base URL is reachable and correct for the target environment
- User-provided credentials work for manual login
- Authentication flow verified manually
- Test data/seeding strategy confirmed
- API bypass endpoints identified (if applicable)
Usage
# Basic setup (auto-detects framework)
/playwright-integration setup
# Specific focus
/playwright-integration configure for React Next.js
/playwright-integration auth handling
/playwright-integration selectors
/playwright-integration debug flaky tests
# Override detection if needed
/playwright-integration --framework=react setup
Example Responses
React + Vite Project
📦 Detected: React 18 + TypeScript + Vite + MUI + React Router
Config recommendations:
- webServer.command: npm run dev (port 5173)
- Use RTL selectors: getByRole, getByTestId
- Add data-testid to MUI components
- Handle React StrictMode double renders
What ships with it
1 file 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.
- 7d ago First seen · 158 lines · 0 tokens per session scan A 8ebc17b27c4b
playwright-integration is a skill published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 158 tokens to every session and 1,296 once invoked, about $0.0008 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-03.
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…