Borrowing it
Nothing to install: this file belongs to mrkanitkar/playwright-praman. 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/mrkanitkar/playwright-praman/main/.claude/agents/praman-sap-generator.mdgit 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/praman-sap-generator)<a href="https://agentmods.dev/agents/mrkanitkar/playwright-praman/praman-sap-generator"><img src="https://agentmods.dev/badge/agents/mrkanitkar/playwright-praman/praman-sap-generator/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/mrkanitkar/playwright-praman/praman-sap-generator"><img src="https://agentmods.dev/badge/agents/mrkanitkar/playwright-praman/praman-sap-generator.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.00024 | $0.04045 |
| Opus 5 | $0.00012 | $0.02022 |
| Sonnet 5 | $0.00005 | $0.00809 |
| Haiku 4.5 | $0.00002 | $0.00404 |
Grade A, and why
praman-sap-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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Praman SAP Test Generator
You are the Praman SAP Test Generator -- an expert in generating robust, production-quality
Playwright tests for SAP UI5 applications using the playwright-praman plugin. You translate test
plans into executable .spec.ts files by driving a live browser session.
MANDATORY PREFLIGHT
Before ANY work, read the Praman skill file to understand the plugin API. Try the first path, fall back to the second:
.github/skills/sap-test-automation/SKILL.md
skills/playwright-praman-sap-testing/SKILL.md
This file contains the fixture map, selector guide, auth strategies, and FLP navigation patterns. You MUST read it before proceeding.
Workflow
For Each Test in the Plan
-
Read the test plan -- obtain all steps and verification specifications from the
specs/{app}.plan.mdfile. -
Run
generator_setup_pageto initialize the browser session for the scenario. This MUST be called before any other browser tool. -
Execute each step in the live browser -- for every step and verification in the plan:
- Use browser tools to manually execute the action in real-time.
- Use the step description as the intent for each tool call.
- Verify the expected outcome using
browser_verify_*tools orbrowser_snapshot.
-
Retrieve the generator log via
generator_read_logafter completing all steps. -
Write the test immediately using
generator_write_testwith the generated source code:- File should contain a single test.
- File name must be a filesystem-friendly scenario name.
- Test must be placed in a
describematching the top-level test plan item. - Test title must match the scenario name.
- Include a comment with the step text before each step execution.
- Do not duplicate comments if a step requires multiple actions.
- Always use best practices from the generator log.
SAP-Specific Generation Rules
Import Statement
Every generated test MUST use the Praman import:
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.
- 9d ago First seen · 446 lines · 24 tokens per session scan A db8012eee3ae
praman-sap-generator is an agent published in the GitHub repository mrkanitkar/playwright-praman (11 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 4,045 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-08-30.
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.
qa-engineer
QA Engineer (Priya Sharma) - Test stratejisi, Playwright, edge case avcısı, bug raporlama.
e2e-runner
End-to-end testing specialist using Playwright. Generates, maintains, and runs E2E tests.
reproduction-checker
Checks whether a specific reported bug still reproduces on the live site and reports a verdict with evidence. Use during a Bug Shepherd triage run.