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 saint4ai/onai-vibecoding-skills --skill playwright-testinggit clone --depth 1 https://github.com/saint4ai/onai-vibecoding-skillsWrote 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/saint4ai/onai-vibecoding-skills/playwright-testing)<a href="https://agentmods.dev/skills/saint4ai/onai-vibecoding-skills/playwright-testing"><img src="https://agentmods.dev/badge/skills/saint4ai/onai-vibecoding-skills/playwright-testing.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.00065 | $0.00627 |
| Opus 5 | $0.00032 | $0.00313 |
| Sonnet 5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
playwright-testing 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.
What it actually says
Playwright Testing — агент сам тестирует фронт и бэк
Ты — инженер по автотестам. Покрываешь приложение тестами на Playwright, чтобы каждое изменение проверялось автоматически, без человека.
Что покрываем (тест-пирамида)
- E2E (end-to-end) — главные пользовательские сценарии целиком: открыл сайт → зарегистрировался → создал запись → увидел результат. Playwright реально открывает браузер и кликает как живой человек.
- API / бэкенд — проверка эндпоинтов напрямую (
requestв Playwright): статусы, тело ответа, авторизация, ошибки. - Smoke — быстрый прогон критичных мест после каждого изменения (главная грузится, вход работает, ключевая кнопка жива).
Как делаешь
- Ставишь Playwright:
npm i -D @playwright/test && npx playwright install. - Тесты — в папке
e2e/илиtests/, конфигplaywright.config.ts(baseURL, ретраи, трейсы при падении). - Каждый тест: подготовка → действие → проверка (
expect). Селекторы — по ролям/тексту (getByRole,getByText), не по хрупким CSS. - Для бэкенда —
request.newContext()и проверка ответов API без UI. - Падает — прикладываешь трейс/скриншот как доказательство, чинишь, повторяешь.
CI/CD (автозапуск)
- Добавляешь GitHub Actions workflow (
.github/workflows/e2e.yml): на каждый push/PR —npx playwright test. Красный тест = блок merge. - Это и есть смысл CI/CD: код залит → тесты прогнались сами → если что-то сломалось, узнаёшь сразу, а не от клиента.
Через MCP (агент сам в браузере)
Если подключён браузерный MCP (Playwright/Chrome), агент может сам открывать браузер, кликать и читать страницу — то есть проверять приложение глазами без отдельных тест-файлов. Это для быстрой проверки «вживую»; постоянное покрытие всё равно держим в e2e/.
Доказательство
Тест прошёл = реальная команда + её вывод (npx playwright test → passed), а не слова «работает». Падение — трейс/скриншот + фикс.
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 · 31 lines · 65 tokens per session scan A d404f942e326
playwright-testing is a skill published in the GitHub repository saint4ai/onai-vibecoding-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 627 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-31.
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.