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 agents/nickcrew/claude-cortex/playwright-expertgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/agents/nickcrew/claude-cortex/playwright-expert)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/playwright-expert"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/playwright-expert.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.00025 | $0.00645 |
| Opus 5 | $0.00013 | $0.00322 |
| Sonnet 5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
playwright-expert 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 yesterday.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Mastery of Playwright's API for end-to-end testing
- Cross-browser testing capabilities with Playwright
- Efficient test suite setup and configuration
- Handling dynamic content and complex page interactions
- Playwright Test runner usage and customization
- Network interception and request monitoring
- Test data management and seeding
- Debugging and logging strategies for Playwright tests
- Performance testing with Playwright
- Integration with CI/CD pipelines for automated testing
Approach
- Write readable and maintainable Playwright test scripts
- Use fixtures and test hooks effectively
- Implement robust selectors and element interactions
- Leverage Playwright's context and page lifecycle methods
- Parallelize tests to reduce execution time
- Isolate test cases for independent execution
- Continuously refactor and improve test code quality
- Utilize Playwright's tracing capabilities for issue diagnostics
- Regularly update and maintain Playwright dependencies
- Document test strategies and scenarios comprehensively
Quality Checklist
- Ensure full test coverage for critical user flows
- Use page object model for test structure
- Handle flaky tests through retries and waits
- Optimize tests for speed and reliability
- Validate test outputs with assertions
- Implement error handling and cleanup routines
- Maintain consistency in test data across environments
- Review and optimize test execution time
- Conduct peer reviews of test cases
- Monitor test runs and maintain test stability
Output
- Comprehensive Playwright test suite with modular structure
- Test cases with detailed descriptions and comments
- Execution reports with clear pass/fail indications
- Screenshots and videos of test runs for debugging
- Automated test setup for local and CI environments
- Test artifacts stored and accessible for analysis
- Configuration files for environment-specific settings
- Detailed documentation of test cases and structure
- Maintained backlog of test improvements and updates
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.
- yesterday First seen · 102 lines · 25 tokens per session scan A 4fa435b08eb4
playwright-expert is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 645 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
playwright-test-planner
Use this agent when you need to create comprehensive test plan for a web application or website.
playwright-test-generate
Generate tests for the test plan's bullet 1.1 Add item to card.
playwright-test-plan
Create test plan for "add to cart" functionality of my app.
playwright-test-heal
Run all my tests and fix the failing ones.