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 agentmods add instructions/vasu31dev/playwright-ts-lib/claude-mdgit clone --depth 1 https://github.com/vasu31dev/playwright-ts-libWhat 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 | $0.01019 | $0.01019 |
| Opus 5 | $0.00509 | $0.00509 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
playwright-ts-lib CLAUDE.md 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 3d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project: vasu-playwright-utils
Playwright TypeScript utility library providing reusable helper methods for browser automation and testing.
Build & Run
- Build:
npm run build(runstsc -p tsconfig.build.json, cleansdist/first) - Type check:
npm run validate(runstsc --noEmit) - Clean:
npm run clean(removesdist/) - Full reset:
npm run ready(removes dist, node_modules, reinstalls, validates, builds, tests)
Test
- All tests:
npm test(Playwright Test) - Chromium only:
npm run test:chromium - Headed (local dev):
npm run local - Smoke/Regression:
npm run test:smoke,npm run test:reg
Lint & Format
- Lint:
npm run lint - Lint fix:
npm run lint:fix - Format:
npm run format(Prettier)
Architecture
src/vasu-playwright-lib/
index.ts # Main entry, re-exports everything
utils/
action-utils.ts # click, fill, hover, drag, alerts, download, upload
assert-utils.ts # expectElement*, expectPage* assertions
locator-utils.ts # getLocator, getLocatorByRole/Text/TestId, frames
element-utils.ts # getText, isElementVisible, waitForElement*
page-utils.ts # setPage/getPage, gotoURL, navigation, switchPage
api-utils.ts # getRequest, postRequest, putRequest, deleteRequest
types/
optional-parameter-types.ts # All option types (ClickOptions, FillOptions, etc.)
constants/ # Timeouts, load state defaults
setup/ # Test setup helpers, custom logger
Subpath Exports
Consumers can import from the main package or specific subpaths:
import { click, fill } from 'vasu-playwright-utils';
import { click } from 'vasu-playwright-utils/action-utils';
import { expectElementToBeVisible } from 'vasu-playwright-utils/assert-utils';
Coding Conventions
- All exported functions have JSDoc comments
- Functions are
asyncand acceptstring | Locatoras input - Options use the pattern:
options?: XxxOptions(intersection types from Playwright + custom extensions) - Visibility is enforced by default (
onlyVisible: true); callers can opt out with{ onlyVisible: false } setPage(page)must be called before using any utility functions
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.
- 3d ago First seen · 88 lines · 1,019 tokens per session scan A f238020c4ab8
playwright-ts-lib CLAUDE.md is an instructions file published in the GitHub repository vasu31dev/playwright-ts-lib (25 stars, last pushed 5mo ago), licensed MIT. It adds 1,019 tokens to every session, about $0.0051 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 instructions, from other repositories
agentic-playwright selectors.instructions.md
Instructions for idavidov13/agentic-playwright, covering selector strategy, critical, instructions, phase 1: open and authenticate and phase 2: explore like a user.
agentic-playwright playwright-cli.instructions.md
Instructions for idavidov13/agentic-playwright, covering browser automation with playwright-cli, quick start, open new browser, navigate to a page and interact with the page using refs from the snapshot.
antigravity-testing-kit GEMINI.md
Instructions for anhtester/antigravity-testing-kit, covering gemini ai - global automation agent rules, git pull restriction rule, browser rules (mandatory), 🖥️ viewport & mode and 🔄 thứ tự debug bắt buộc (playwright mcp).
Vigilis AGENTS.md
Instructions for piyushpathakqa/Vigilis, covering what this project is, where to find things, the one-sentence architecture, conventions and commands.
mcp-ie-migration-vrt AGENTS.md
AGENTS.md instructions for rayven122/mcp-ie-migration-vrt, covering agents.md, file map, architecture, conventions and adding a tool.
qa-use CLAUDE.md
Instructions for desplega-ai/qa-use, covering claude.md, project map and tech stack.