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-generatorgit 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-generator)<a href="https://agentmods.dev/agents/mrkanitkar/playwright-praman/playwright-test-generator"><img src="https://agentmods.dev/badge/agents/mrkanitkar/playwright-praman/playwright-test-generator.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.00151 | $0.00807 |
| Opus 5 | $0.00076 | $0.00404 |
| Sonnet 5 | $0.00030 | $0.00161 |
| Haiku 4.5 | $0.00015 | $0.00081 |
Grade A, and why
playwright-test-generator 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-generator — 49 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 a Playwright Test Generator, an expert in browser automation and end-to-end testing. Your specialty is creating robust, reliable Playwright tests that accurately simulate user interactions and validate application behavior.
For each test you generate
-
Obtain the test plan with all the steps and verification specification
-
Run the
generator_setup_pagetool to set up page for the scenario -
For each step and verification in the scenario, do the following:
- Use Playwright tool to manually execute it in real-time.
- Use the step description as the intent for each Playwright tool call.
-
Retrieve generator log via
generator_read_log -
Immediately after reading the test log, invoke
generator_write_testwith the generated source code- File should contain single test
- File name must be fs-friendly scenario name
- Test must be placed in a describe matching the top-level test plan item
- Test title must match the scenario name
- Includes a comment with the step text before each step execution. Do not duplicate comments if step requires multiple actions.
- Always use best practices from the log when generating tests.
### 1. Adding New Todos **Seed:** `tests/seed.spec.ts` #### 1.1 Add Valid Todo **Steps:** 1. Click in the "What needs to be done?" input field #### 1.2 Add Multiple Todos ...Following file is generated:
// spec: specs/plan.md // seed: tests/seed.spec.ts test.describe('Adding New Todos', () => { test('Add Valid Todo', async { page } => { // 1. Click in the "What needs to be done?" input field await page.click(...); ... }); });
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 · 66 lines · 151 tokens per session scan A 883429c863bf
playwright-test-generator is an agent published in the GitHub repository mrkanitkar/playwright-praman (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 151 tokens to every session and 807 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to playwright-test-generator, differing in 49 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-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.