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 rules/mrkanitkar/playwright-praman/cursor-rules-appendablegit clone --depth 1 https://github.com/mrkanitkar/playwright-pramanWhat 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.00000 | $0.00268 |
| Opus 5 | $0.00000 | $0.00134 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
cursor-rules-appendable 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 2d 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.
What it actually says
Praman + Playwright SAP Test Automation
Primary skill reference: node_modules/playwright-praman/skills/playwright-praman-sap-testing/SKILL.md
Read this file before generating any SAP UI5 test. SAP pages are hybrid — use Praman fixtures for UI5 controls, Playwright native for login forms, Web Components, and plain DOM.
Mandatory Import
import { test, expect } from 'playwright-praman';
Core Rules
- UI5 controls → Praman fixtures (
ui5.control()+ proxy methods) - Non-UI5 → Playwright native (
page.locator()); NEVER native for UI5 (page.click('#__...'),.sapM...) - Input pattern:
setValue()+fireChange()+waitForUI5()always together - Auth in seed file ONLY — never in test body
- Include TSDoc compliance header in every generated test
Quick Reference
node_modules/playwright-praman/skills/playwright-praman-sap-testing/ai-quick-reference.md
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.
- 2d ago First seen · 32 lines · 0 tokens per session scan A 983d1870a670
cursor-rules-appendable is a cursor rule published in the GitHub repository mrkanitkar/playwright-praman (11 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 268 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
Comprehensive Testing Best Practices for Svelte 5 + vitest-browser-svelte.
cursorrules
Comprehensive Testing Best Practices for Svelte 5 + vitest-browser-svelte.
cursor-rules
Playwright E2E testing patterns, conventions, and best practices.
playwright-agents
Playwright test agent workflows for planning, generating, and healing tests.
vasu-playwright-utils
Use vasu-playwright-utils for Playwright tests. Follow locator strategy (data-testid, role, label). Use with playwright-cli to verify flows.
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.