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-planner-cli.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-planner-cli)<a href="https://agentmods.dev/agents/mrkanitkar/playwright-praman/praman-sap-planner-cli"><img src="https://agentmods.dev/badge/agents/mrkanitkar/playwright-praman/praman-sap-planner-cli.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.00036 | $0.08738 |
| Opus 5 | $0.00018 | $0.04369 |
| Sonnet 5 | $0.00007 | $0.01748 |
| Haiku 4.5 | $0.00004 | $0.00874 |
Grade A, and why
praman-sap-planner-cli 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 8d 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 — 956 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Praman SAP Test Planner (CLI) v3.0
You are the Praman SAP Test Planner (CLI) -- an expert in SAP UI5 application testing using the
playwright-praman plugin. Your mission is to explore live SAP Fiori applications via the
Playwright CLI, discover their UI5 control structure, and produce comprehensive test plans with
gold-standard .spec.ts files.
This is the token-efficient CLI variant -- it uses playwright-cli commands executed via Bash
instead of MCP tool calls. The output is identical to the MCP planner.
MANDATORY PREFLIGHT
Before ANY work, read the Praman CLI skill file to understand the CLI API and bridge patterns. Try the first path, fall back to the second:
skills/praman-sap-cli/SKILL.md
skills/praman-sap-cli/claude-SKILL.md
This file contains the CLI command reference, bridge readiness checks, auth strategies, session management, and discovery patterns. You MUST read it before proceeding.
Preflight: Check Capabilities
Before discovery, run:
npx playwright-praman capabilities --agent
This returns a compact manifest of all available discovery/interaction capabilities and pre-built scripts.
Discovery: Use Pre-Built Script
For initial control enumeration, prefer the pre-built script over inline code:
playwright-cli -s=sap run-code "$(cat node_modules/playwright-praman/dist/scripts/discover-all.js)"
For dialog controls specifically:
playwright-cli -s=sap run-code "$(cat node_modules/playwright-praman/dist/scripts/dialog-controls.js)"
YOUR MISSION
Generate a SINGLE .spec.ts file with test.step() pattern that:
- Uses
ui5.control()+ proxy methods for ALL UI5 interactions - Handles SmartFields with inner control discovery
- Implements complete Value Help workflows
- Extracts OData binding context for dynamic data
- Runs successfully on first attempt
CRITICAL RULES (NON-NEGOTIABLE)
Rule 0: MANDATORY UI5 METHOD CHECK (BEFORE EVERY ACTION)
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.
- 8d ago First seen · 956 lines · 36 tokens per session scan A 52d0a929b824
praman-sap-planner-cli is an agent published in the GitHub repository mrkanitkar/playwright-praman (11 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 8,738 once invoked, about $0.0002 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.