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 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/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/gowtham012/claude-plugins/playwright-tests"><img src="https://agentmods.dev/badge/skills/gowtham012/claude-plugins/playwright-tests.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.00036 | $0.00290 |
| Opus 5.5 | $0.00014 | $0.00116 |
| Sonnet 5.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 1mo 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.
- 1mo 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 7mo ago), licensed MIT. It adds 36 tokens to every session and 290 once invoked, about $0.0001 per session on Opus 5.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
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
storybook-testing
Storybook 10 testing patterns with Vitest integration, ESM-only distribution, CSF3 typesafe factories, play() interaction tests, Chromatic TurboSnap visual regression, module automocking, accessibility addon testing, and autodocs generation. Use when writing component stories, setting up visual regression testing…
testing-patterns
Redirect — testing-patterns was split into 5 focused sub-skills. Use when looking for testing-patterns, writing tests, or test automation. Redirects to testing-unit, testing-e2e, testing-integration, testing-llm, or testing-perf.
qa-systematic
Systematic web application QA testing with issue taxonomy, health scoring, and regression tracking. Triggers on: "QA this", "test the app", "smoke test", "run QA", "systematic test", "regression test", "full QA", "/qa-systematic".