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 pw-framework-toolinggit 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/pw-framework-tooling)<a href="https://agentmods.dev/skills/mallikarjun-roddannavar/playwright-agentic-automation/pw-framework-tooling"><img src="https://agentmods.dev/badge/skills/mallikarjun-roddannavar/playwright-agentic-automation/pw-framework-tooling/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/pw-framework-tooling"><img src="https://agentmods.dev/badge/skills/mallikarjun-roddannavar/playwright-agentic-automation/pw-framework-tooling.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.00072 | $0.00602 |
| Opus 5 | $0.00036 | $0.00301 |
| Sonnet 5 | $0.00014 | $0.00120 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade A, and why
pw-framework-tooling 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 10d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PW Framework Tooling
Maintain the framework infrastructure that supports test execution quality and developer workflow.
Use This Skill When
- Changing
playwright.config.ts,package.json, linting, formatting, typechecking, waits, logging, or reporting. - Adding or updating validation scripts.
- Updating framework documentation about tooling or execution behavior.
Covered Areas
playwright.config.tspackage.jsoneslint.config.mjstsconfig.jsonutils/common/Logger.tsutils/common/Waits.tsutils/common/CustomReporter.tsscripts/checkNamingConventions.mjs- framework README quality/tooling sections
Follow These Rules
- Keep
config/test-config.jsonas the single config source for base URLs, role credentials, and shared waits. - Keep framework timeout derivation in
utils/common/Waits.ts. - Keep scoped logging via
logger.withScope(...). - Keep the custom reporter at
utils/common/CustomReporter.ts. - Keep ESLint, Prettier, and
tsc --noEmitworking together. - Keep
@typescript-eslint/no-floating-promisesenabled. - Keep
npm run check:namingpassing for framework naming rules.
Inspect First
- Identify the smallest set of tooling files that own the behavior.
- Check whether the change is configuration, validation, runtime helper, or documentation.
- Reuse an existing script or helper before adding a new one.
- Keep claims in docs limited to what the framework actually implements.
Preferred Change Order
- Change configuration or shared helper logic first.
- Change scripts next if deterministic enforcement is needed.
- Update documentation last so it reflects the final behavior.
- Avoid spreading the same rule across multiple files unless each layer truly needs it.
Validation Workflow
Prefer direct local binaries if npm run is unreliable in the AI shell:
node ./scripts/checkNamingConventions.mjs./node_modules/.bin/eslint.cmd ../node_modules/.bin/tsc.cmd --noEmit./node_modules/.bin/prettier.cmd . --check./node_modules/.bin/playwright.cmd test --list
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.
- 10d ago First seen · 70 lines · 72 tokens per session scan A 3bc84adb2d6b
pw-framework-tooling is a skill published in the GitHub repository Mallikarjun-Roddannavar/playwright-agentic-automation (11 stars, last pushed 4d ago), licensed MIT. It adds 72 tokens to every session and 602 once invoked, about $0.0004 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
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.