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/testsgit 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.00326 |
| Opus 5 | $0.00000 | $0.00163 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
tests 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
Test Rules
Unit Tests (Vitest)
- File pattern:
*.test.ts - Hermetic: no network, no SAP system
- Use
describe/itpattern - Mock bridge with typed test doubles from
tests/helpers/ - Coverage ≥ 90% statements, ≥ 85% branches
Integration Tests (Playwright)
- File pattern:
*.spec.ts - Use
test.step()for each logical step - NEVER use
page.waitForTimeout()— usewaitForUI5Stable() - Require SAP credentials in environment
Correct Pattern
import { describe, expect, it, vi } from 'vitest';
describe('MyModule', () => {
it('should handle the expected case', () => {
const result = myFunction(input);
expect(result).toBe(expected);
});
it('should throw PramanError on failure', () => {
expect(() => myFunction(badInput)).toThrow(PramanError);
});
});
Forbidden in Tests
anytype assertionsconsole.log(use test assertions)page.waitForTimeout()(usewaitForUI5Stable())- Raw
throw new Error()(use typed error subclass) require()in test source (ESM only)
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 · 48 lines · 0 tokens per session scan A 1879849c53b2
tests is a cursor rule published in the GitHub repository mrkanitkar/playwright-praman (11 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 326 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
cursorrules
Comprehensive Testing Best Practices for Svelte 5 + vitest-browser-svelte.
standards
Repo-wide coding standards.
testing
Comprehensive Testing Best Practices for Svelte 5 + vitest-browser-svelte.
project
Project-wide instructions and conventions.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.