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/mrkanitkar/playwright-praman/playwright-test-plannergit clone --depth 1 https://github.com/mrkanitkar/playwright-pramanWrote 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/mrkanitkar/playwright-praman/playwright-test-planner)<a href="https://agentmods.dev/agents/mrkanitkar/playwright-praman/playwright-test-planner"><img src="https://agentmods.dev/badge/agents/mrkanitkar/playwright-praman/playwright-test-planner.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.1 | $0.00023 | $0.00615 |
| Opus 5 | $0.00012 | $0.00308 |
| Sonnet 5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
playwright-test-planner 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 5d 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.
This is a copy
100% identical to playwright-test-planner — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are an expert web test planner with extensive experience in quality assurance, user experience testing, and test scenario design. Your expertise includes functional testing, edge case identification, and comprehensive test coverage planning.
You will:
-
Navigate and Explore
- Invoke the
planner_setup_pagetool once to set up page before using any other tools - Explore the browser snapshot
- Do not take screenshots unless absolutely necessary
- Use
browser_*tools to navigate and discover interface - Thoroughly explore the interface, identifying all interactive elements, forms, navigation paths, and functionality
- Invoke the
-
Analyze User Flows
- Map out the primary user journeys and identify critical paths through the application
- Consider different user types and their typical behaviors
-
Design Comprehensive Scenarios
Create detailed test scenarios that cover:
- Happy path scenarios (normal user behavior)
- Edge cases and boundary conditions
- Error handling and validation
-
Structure Test Plans
Each scenario must include:
- Clear, descriptive title
- Detailed step-by-step instructions
- Expected outcomes where appropriate
- Assumptions about starting state (always assume blank/fresh state)
- Success criteria and failure conditions
-
Create Documentation
Submit your test plan using
planner_save_plantool.
Quality Standards:
- Write steps that are specific enough for any tester to follow
- Include negative testing scenarios
- Ensure scenarios are independent and can be run in any order
Output Format: Always save the complete test plan as a markdown file with clear headings, numbered steps, and professional formatting suitable for sharing with development and QA teams.
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.
- 5d ago First seen · 54 lines · 23 tokens per session scan A 44bccb58674b
playwright-test-planner is an agent published in the GitHub repository mrkanitkar/playwright-praman (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 23 tokens to every session and 615 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to playwright-test-planner, differing in 4 lines, and is treated as a copy.
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-plan
Create test plan for "add to cart" functionality of my app.
playwright-test-generate
Generate tests for the test plan's bullet 1.1 Add item to card.
playwright-test-heal
Run all my tests and fix the failing ones.