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 skills/gowtham012/claude-plugins/playwright-testsnpx skills add gowtham012/Claude-plugins --skill playwright-testsgit clone --depth 1 https://github.com/gowtham012/Claude-pluginsWrote 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/gowtham012/claude-plugins/playwright-tests)<a href="https://agentmods.dev/skills/gowtham012/claude-plugins/playwright-tests"><img src="https://agentmods.dev/badge/skills/gowtham012/claude-plugins/playwright-tests.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 | $0.00036 | $0.00290 |
| Opus 5 | $0.00018 | $0.00145 |
| Sonnet 5 | $0.00007 | $0.00058 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
playwright-tests 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 4d 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
Generate Playwright tests from video: $ARGUMENTS
Steps
- Call MCP tool
mcp__video-insight__generate_testswithvideo_path=$0andframework="playwright". - Read keyframe images for each step to identify exact selectors (button text, roles, test-ids).
- Map each
inferred_action:navigate→await page.goto()orexpect(page).toHaveURL()click_or_submit→await page.locator('text=...').click()scroll→await page.evaluate(() => window.scrollBy(0, 500))observe→await expect(page.locator('text=...')).toBeVisible()
- Use
text_appearedfortoBeVisible(),text_disappearedfortoBeHidden(). - Wrap in
describe/testblocks. Output a single.spec.tsfile.
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.
- 4d ago First seen · 22 lines · 36 tokens per session scan A 9062d8c3d067
playwright-tests is a skill published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 290 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-08-31.
Other skills, from other repositories
nexu-e2e-test
Use when verifying OpenClaw gateway fixes end-to-end, testing skill loading after restart, or running integration tests against the local Nexu+OpenClaw stack. Triggers on "e2e test", "verify fix", "test gateway", "test skills loading".
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.
integration
Run integration and e2e tests after unit tests pass. Use after /supergraph:fix when unit tests are green.
testing-strategy
Test pyramid, coverage targets, and test patterns (unit/integration/E2E). TRIGGER when: planning tests, writing test code, or reviewing coverage. SKIP: quality-gate scoring of plans (use quality-validation); security testing (use security-review-checklists). (Examples use common runners such as pytest and vitest.).
pdlc-quality
Skill "pdlc-quality" from kanfu-panda/pdlc-skills, covering 质量闸门与报告, 这个命令的立身之本, 前置：两份真源, --init：首次建立目标声明 and 段一：跑真实 check.
moodle-behat-testing
Use when writing or running Behat acceptance tests for Moodle plugins. Covers feature files, custom step definitions, tags, data generators in Background, JavaScript scenarios, and Selenium/Chromedriver setup.