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.
git 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/rules/mrkanitkar/playwright-praman/praman-cli)<a href="https://agentmods.dev/rules/mrkanitkar/playwright-praman/praman-cli"><img src="https://agentmods.dev/badge/rules/mrkanitkar/playwright-praman/praman-cli/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/rules/mrkanitkar/playwright-praman/praman-cli"><img src="https://agentmods.dev/badge/rules/mrkanitkar/playwright-praman/praman-cli.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.00747 |
| Opus 5.5 | $0.00000 | $0.00299 |
| Sonnet 5.5 | $0.00000 | $0.00149 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
praman-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 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Praman CLI — SAP UI5 Testing Patterns
Token-efficient CLI alternative to MCP. Bridge object: window.__praman_bridge.
Bridge Readiness Check
Always verify the bridge is ready before interacting with controls:
npx playwright-cli run-code -s=sap "async page => {
const ready = await page.evaluate(() => window.__praman_bridge?.ready);
return ready;
}"
Never proceed if ready is not true. The bridge is injected via browser.initScript in .playwright/praman-cli.config.json.
Control Discovery via run-code
Use getById() to locate UI5 controls. Always return values — console.log() output is invisible to the agent.
npx playwright-cli run-code -s=sap "async page => {
const ctrl = await page.evaluate(() =>
window.__praman_bridge.getById('container-app---main--myInput')
);
return ctrl;
}"
WARNING: console.log() Is Invisible
console.log() inside run-code produces NO output for the agent. Always use return to surface results.
// WRONG — agent sees nothing
async page => { console.log(await page.evaluate(() => ...)); }
// CORRECT — agent receives the value
async page => { return await page.evaluate(() => ...); }
setValue + fireChange + waitForUI5 Pattern
Every input interaction requires all three steps — never skip fireChange() or waitForUI5():
npx playwright-cli run-code -s=sap "async page => {
await page.evaluate(() => {
const ctrl = window.__praman_bridge.getById('container-app---main--inputField');
ctrl.setValue('test value');
ctrl.fireChange({ value: 'test value' });
});
await page.evaluate(() => window.__praman_bridge.waitForUI5());
return 'input set';
}"
Snapshot: Always Use --filename
Agents MUST use --filename so the snapshot is written to a deterministic path they can read back:
npx playwright-cli snapshot -s=sap --filename=current-state.txt
Without --filename, the snapshot goes to stdout and may be truncated or lost in large outputs.
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 · 95 lines · 0 tokens per session scan A 7fbfb7b48728
praman-cli is a cursor rule published in the GitHub repository mrkanitkar/playwright-praman (10 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 747 tokens. 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 cursor rules, from other repositories
testing
Shared Svelte testing guidance.
cursor-rules
Playwright E2E testing rules for {{PROJECTNAME}}; the full skill lives in .agents/skills/playwright-e2e.
playwright-agents
Playwright test agent workflows for planning, generating, and healing tests.
component-patterns
React Component Patterns.
rule-06
This is test rule number in the large package scalability test.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.