playwright-praman: Agent for Claude Code

.claude/agents/praman-sap-generator.md

praman-sap-generator is an agent for Claude Code from mrkanitkar/playwright-praman. It costs 24 tokens per session (4,045 once invoked), scanned A, original, Apache-2.0.

A test-generation assistant for SAP UI5 applications, which are web applications built with SAP’s user-interface framework. It turns written test plans into Playwright browser tests using Praman fixtures and live browser checks.

In plain words
What is it for?
Use it to create executable TypeScript Playwright tests from application test plans, including navigation, user actions, and verification steps in a live SAP browser session.
Why use it?
It connects test descriptions with actual browser actions and verifies each scenario while generating the test file. Its required setup and selector guidance help tests follow the application’s SAP navigation patterns.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is mrkanitkar/playwright-praman's own configuration. It tells Claude Code how to work on playwright-praman itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything playwright-praman configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/mrkanitkar/playwright-praman/main/.claude/agents/praman-sap-generator.md
Clone the repo
git clone --depth 1 https://github.com/mrkanitkar/playwright-praman

Made for: Claude Code.

Wrote 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.

agentmods badge for praman-sap-generator

README.md
[![agentmods](https://agentmods.dev/badge/agents/mrkanitkar/playwright-praman/praman-sap-generator/github.svg)](https://agentmods.dev/agents/mrkanitkar/playwright-praman/praman-sap-generator)
Your own site
<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.

agentmods 80×15 button for praman-sap-generator

Your own site · 80×15
<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>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,045 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash db8012eee3ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

.claude/agents/praman-sap-generator.md · 446 lines

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

  1. Read the test plan -- obtain all steps and verification specifications from the specs/{app}.plan.md file.

  2. Run generator_setup_page to initialize the browser session for the scenario. This MUST be called before any other browser tool.

  3. 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 or browser_snapshot.
  4. Retrieve the generator log via generator_read_log after completing all steps.

  5. Write the test immediately using generator_write_test with 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 describe matching 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:

Read the full file on GitHub · 446 lines

Changes

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.

  1. 9d ago First seen · 446 lines · 24 tokens per session scan A db8012eee3ae

Subscribe to this mod's changes

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.