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 katalon-labs/true-skills --skill playwright-executegit clone --depth 1 https://github.com/katalon-labs/true-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/katalon-labs/true-skills/playwright-execute)<a href="https://agentmods.dev/skills/katalon-labs/true-skills/playwright-execute"><img src="https://agentmods.dev/badge/skills/katalon-labs/true-skills/playwright-execute/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/katalon-labs/true-skills/playwright-execute"><img src="https://agentmods.dev/badge/skills/katalon-labs/true-skills/playwright-execute.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.00122 | $0.01291 |
| Opus 5 | $0.00061 | $0.00646 |
| Sonnet 5 | $0.00024 | $0.00258 |
| Haiku 4.5 | $0.00012 | $0.00129 |
Grade A, and why
playwright-execute 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 9d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katalon Playwright Execute
Use this skill when the user asks to execute a Playwright script/suite and send results to Katalon True Platform. The workflow is not complete until local execution finishes, report artifacts are collected, and upload is either verified or clearly blocked.
Execution Workflow
+------------------+ --> +------------------+ --> +------------------+
| Resolve target | | Preflight repo | | Configure report |
+------------------+ +------------------+ +------------------+
|
v
+------------------+ <-- +------------------+ <-- +------------------+
| Verify Platform | | Upload report | | Run Playwright |
+------------------+ +------------------+ +------------------+
Required Context
Resolve or ask for only missing required values:
- Playwright target: spec file, grep, project, package script, suite command, or user-provided command.
- Repository/root directory that contains
package.jsonand Playwright config. - Katalon Platform project ID. Use Katalon MCP
list_projectswhen available. - Katalon API key from a secure source such as
KATALON_API_KEY; check whether it is already available before asking. - Platform base URL only when non-default or when the project uses QA/prod custom domains.
- Whether the agent may modify Playwright config/package files if the Katalon reporter is missing.
Treat the human as a tool: ask concise questions when target, credentials, project, or permission cannot be resolved safely. Never ask the user to paste secrets into normal chat when a secure secret mechanism or environment variable can be used.
Preflight
Before running:
- Inspect the repository for
package.json,playwright.config.*,@playwright/test, existing reporters, package manager lockfiles, and scripts. - Verify Node.js is version 18 or newer when possible.
- Check for
KATALON_API_KEYin the current process environment or the repo's approved secret mechanism before composing any upload command. - If
KATALON_API_KEYis missing, stop before execution/upload and ask the user to provide it through a secure environment variable or secret mechanism. - Run dependency installation only when the repo convention is clear and the user has allowed dependency changes.
- Confirm
@katalon/playwright-reporteris installed or can be installed. - Verify a deterministic report output directory, preferably
./reportsor the repo's existing Katalon report directory. - Build commands with secrets redacted in user-facing output.
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.
- 9d ago First seen · 100 lines · 122 tokens per session scan A 2ad9e7de6fd7
playwright-execute is a skill published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed 2d ago), licensed MIT. It adds 122 tokens to every session and 1,291 once invoked, about $0.0006 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
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.
Console Error Hunter
Systematically detect, capture, and categorize browser console errors, warnings, and unhandled exceptions during automated test execution.
playwright-e2e
Comprehensive end-to-end testing skill using Playwright for web applications, covering page objects, selectors, assertions, waits, fixtures, and test organization.
e2e-testing-claude-code
Make Claude Code write and maintain end-to-end tests like a senior SDET — Playwright and Cypress flows with stable locators, the Page Object Model, fixtures, reused auth state, network mocking, and flake-free CI. Claude Code E2E testing, done right.
Browser Agent QA Testing
Teach agents to use AI browser agents for exploratory and smoke QA with step budgets, evidence-based assertions, guardrails, and Playwright conversion.
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…