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 Mallikarjun-Roddannavar/playwright-agentic-automation --skill playwright-agenticgit clone --depth 1 https://github.com/Mallikarjun-Roddannavar/playwright-agentic-automationWrote 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/mallikarjun-roddannavar/playwright-agentic-automation/playwright-agentic)<a href="https://agentmods.dev/skills/mallikarjun-roddannavar/playwright-agentic-automation/playwright-agentic"><img src="https://agentmods.dev/badge/skills/mallikarjun-roddannavar/playwright-agentic-automation/playwright-agentic/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/mallikarjun-roddannavar/playwright-agentic-automation/playwright-agentic"><img src="https://agentmods.dev/badge/skills/mallikarjun-roddannavar/playwright-agentic-automation/playwright-agentic.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.00031 | $0.00625 |
| Opus 5 | $0.00015 | $0.00313 |
| Sonnet 5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
playwright-agentic 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Agentic
Use this entry skill inside a checkout of playwright-agentic-automation when a task spans framework conventions, product behavior, UI/API automation, or impact analysis. It is a routing guide for an external coding agent; it does not invoke an LLM or make changes automatically.
Start safely
- Read
AGENTS.mdfor repository-wide ownership and validation rules. - Run
npm run agent:doctorbefore runtime work when the environment may be new or stale. - For a feature question or impact analysis, read
knowledge/index.md, runnpm run knowledge:check, and query the narrowest relevant term withnpm run knowledge:query -- <term>ornpm run knowledge:impact -- <term>.
Route by work type
- UI Page Objects, UI specs, selectors, or navigation: read
.agents/skills/pw-ui-pom/SKILL.md. - API services/specs, fixtures, or authentication: read
.agents/skills/pw-api-pom/SKILL.md. - Scripts, Playwright configuration, linting, reporting, or README tooling claims: read
.agents/skills/pw-framework-tooling/SKILL.md. - Knowledge freshness, source relationships, traceability, or impact: read
.agents/skills/codebase-second-brain/SKILL.md. - A cross-layer failure involving UI, API, data, or Playwright evidence: read
.agents/skills/full-stack-incident-analyst/SKILL.md. - A failed Playwright test, diagnosis-only request, or guarded test repair: read
.agents/skills/qa-safe-healing/SKILL.md, then treatqa/failure-taxonomy.jsonandqa/evidence-schema.jsonas the policy source of truth.
Use the narrowest relevant skill. When a task spans layers, use the knowledge skill first and then the owning implementation skill.
Evidence boundary
Treat source code, configuration, and executed tests as authoritative. The generated knowledge graph is static evidence, not proof that a path ran. Keep selectors in Page Objects, assertions in tests, and business-meaning changes under human review before they enter active product knowledge.
For a failure, diagnose before modifying. Preserve evidence, classify it, and obey the resulting modification decision. Never weaken assertions, skip/fixme/delete tests, swallow failures, or force actions merely to obtain green output. Run npm run qa:guardrails before accepting a repair.
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.
- 3d ago First seen · 38 lines · 31 tokens per session scan A 3f9becf97222
playwright-agentic is a skill published in the GitHub repository Mallikarjun-Roddannavar/playwright-agentic-automation (11 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 625 once invoked, about $0.0002 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-08.
Other skills, from other repositories
verify
How to run and drive this app to verify UI/server changes at runtime.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.