Borrowing it
Nothing to install: this file belongs to layer1labs/specsmith. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/layer1labs/specsmith/main/.agents/skills/playwright-testing/SKILL.mdgit clone --depth 1 https://github.com/layer1labs/specsmithWrote 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/layer1labs/specsmith/playwright-testing)<a href="https://agentmods.dev/skills/layer1labs/specsmith/playwright-testing"><img src="https://agentmods.dev/badge/skills/layer1labs/specsmith/playwright-testing/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/layer1labs/specsmith/playwright-testing"><img src="https://agentmods.dev/badge/skills/layer1labs/specsmith/playwright-testing.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.00019 | $0.00385 |
| Opus 5.5 | $0.00008 | $0.00154 |
| Sonnet 5.5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
playwright-testing 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 2mo 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
Playwright Testing Framework
This skill enables specsmith projects to use Playwright for end-to-end browser testing while maintaining governance compliance.
Requirements Covered
- REQ-101: Playwright Testing Framework
- Allows specsmith projects to use Playwright for end-to-end browser testing with human approval
Integration Capabilities
Framework Features
- End-to-end browser testing with Playwright
- Cross-browser testing (Chromium, Firefox, WebKit)
- API testing capabilities
- Screenshot and video capture
- Parallel test execution
- Test reporting and analytics
Governance Requirements
- Human approval required for all Playwright testing
- Configuration management with governance controls
- Test artifact management with approval
- Reporting and coverage tracking with approval
Usage Examples
# Initialize Playwright testing
specsmith skill install playwright-testing
# Configure Playwright settings
specsmith playwright configure --browser chromium --timeout 30000
# Run end-to-end tests
specsmith playwright run --test-suite e2e-tests
# Generate test reports
specsmith playwright report --format html
Configuration
The skill requires the following configuration in scaffold.yml:
playwright:
browser: chromium
timeout: 30000
headless: true
parallel: true
screenshot: "on_failure"
Security Considerations
- All Playwright testing requires human approval
- Test environment isolation must be maintained
- Sensitive data handling in tests must be secured
- Test artifact access controls must be enforced
Compliance Requirements
- Follow security best practices for testing environments
- Maintain audit logs of all Playwright test executions
- Ensure proper test artifact management and retention
- Generate and track test coverage reports
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.
- 2mo ago First seen · 73 lines · 19 tokens per session scan A 017db689ef4e
playwright-testing is a skill published in the GitHub repository layer1labs/specsmith (8 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 385 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
responsive-audit
Responsive audit: test pages at 375/768/1024px breakpoints via Playwright. Checks overflow, tap targets, sidebar collapse, text reflow, WCAG 1.4.4 zoom.
e2e-browser-test
Use when a ticket asks for end-to-end or browser coverage of a user journey — sign-up, checkout, a form submission, a dashboard flow — driven through the real UI with Playwright, Cypress, or the repo's browser harness. Invoke for "add an e2e test", "cover the flow in the browser", or when an acceptance criterion can…
build-verification-skill
Build this project's verification skill - a small CLI that drives the running app and captures evidence, plus a feature map of what exists and how to reach it - and the CI check that keeps the map current. Use when asked to 'build a verification skill', 'let the agent drive the app', 'make a feature map', 'the agent…
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.
e2e-testing-standards
End-to-end testing with Playwright - browser automation, visual regression, test data management.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.