Borrowing it
Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. 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/s-hiraoku/vscode-sidebar-terminal/main/.claude/agents/playwright-test-planner.mdgit clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminalWrote 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/s-hiraoku/vscode-sidebar-terminal/playwright-test-planner)<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/playwright-test-planner"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/playwright-test-planner/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/agents/s-hiraoku/vscode-sidebar-terminal/playwright-test-planner"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/playwright-test-planner.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.00000 | $0.01055 |
| Opus 5.5 | $0.00000 | $0.00422 |
| Sonnet 5.5 | $0.00000 | $0.00211 |
| Haiku 4.5 | $0.00000 | $0.00105 |
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 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.
This is a copy
78% identical to playwright-test-planner — 113 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
Save your test plan as requested:
- Executive summary of the tested page/application
- Individual scenarios as separate sections
- Each scenario formatted with numbered steps
- Clear expected results for verification
Application Overview
The TodoMVC application is a React-based todo list manager that provides core task management functionality. The application features:
- Task Management: Add, edit, complete, and delete individual todos
- Bulk Operations: Mark all todos as complete/incomplete and clear all completed todos
- Filtering: View todos by All, Active, or Completed status
- URL Routing: Support for direct navigation to filtered views via URLs
- Counter Display: Real-time count of active (incomplete) todos
- Persistence: State maintained during session (browser refresh behavior not tested)
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 · 93 lines · 0 tokens per session scan A 93787024c1e3
playwright-test-planner is an agent published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (22 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,055 tokens. A static security scan graded it A with 0 findings. It is 78% identical to playwright-test-planner, differing in 113 lines, and is treated as a copy.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.