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 skills add mrkanitkar/playwright-praman --skill praman-sap-cligit 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/skills/mrkanitkar/playwright-praman/praman-sap-cli)<a href="https://agentmods.dev/skills/mrkanitkar/playwright-praman/praman-sap-cli"><img src="https://agentmods.dev/badge/skills/mrkanitkar/playwright-praman/praman-sap-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/skills/mrkanitkar/playwright-praman/praman-sap-cli"><img src="https://agentmods.dev/badge/skills/mrkanitkar/playwright-praman/praman-sap-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 184 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Output Handling · line 310 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00050 | $0.04790 |
| Opus 5 | $0.00025 | $0.02395 |
| Sonnet 5 | $0.00010 | $0.00958 |
| Haiku 4.5 | $0.00005 | $0.00479 |
Grade A, and why
praman-sap-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 — 602 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP UI5 Test Automation via Playwright CLI
Package: playwright-praman v1.1.2
CLI Requirement: @playwright/cli v0.1.3+ and playwright v1.59+
Purpose: Discover SAP UI5 controls, debug Praman tests, and automate SAP Fiori workflows using the Playwright CLI. Agents use CLI commands for live discovery, then produce Praman fixture code as output.
Setup: Create Config File
Create .playwright/praman-cli.config.json in your project root:
mkdir -p .playwright
cat > .playwright/praman-cli.config.json << 'PRAMAN_EOF'
{
"browser": {
"browserName": "chromium",
"initScript": ["./node_modules/playwright-praman/dist/browser/praman-bridge-init.js"]
},
"timeouts": {
"navigation": 120000
}
}
PRAMAN_EOF
Without
--config: Browser opens fine, page loads fine, butwindow.__praman_bridgeisundefined. All discovery scripts will fail.
eval vs run-code
| Use | Command | Syntax |
|---|---|---|
| Quick check | eval |
playwright-cli eval "() => window.__praman_bridge?.ready" |
| Multi-step | run-code |
playwright-cli run-code "async page => { ... }" |
CRITICAL: eval requires a function wrapper () => expr. Bare expressions will fail.
# ✅ CORRECT
playwright-cli eval "() => window.__praman_bridge?.ready"
# ❌ WRONG — fails silently
playwright-cli eval "window.__praman_bridge?.ready"
run-code rules:
- Only
pageis in scope — noprocess.env, norequire() console.log()is invisible — always usereturnto get data- Return ONLY serializable values: strings, numbers, booleans, null, plain objects, arrays
- Do NOT return: functions, DOM nodes, Symbols, circular references
Discover Controls with Methods
Pre-built Script (recommended)
playwright-cli -s=sap run-code "$(cat node_modules/playwright-praman/dist/scripts/discover-all.js)"
Returns up to 100 controls with IDs, types, properties, and method names.
Inline Alternative
playwright-cli -s=sap run-code "async page => {
return await page.evaluate(() => {
const bridge = window.__praman_bridge;
if (!bridge || !bridge.ready) return { error: 'Bridge not ready' };
return Object.values(sap.ui.require('sap/ui/core/ElementRegistry').all()).slice(0, 100).map(c => ({
id: c.getId(),
type: c.getMetadata().getName(),
methods: bridge.utils.retrieveControlMethods(c.getId())
}));
});
}"
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/control-type-reference.md 21 KB
- references/debug-cli.md 12 KB
- references/eval-patterns.md 1.7 KB
- references/flp-navigation-cli.md 8.8 KB
- references/odata-cli.md 11 KB
- references/praman-bridge-setup.md 7.4 KB
- references/praman-test-debug-cli.md 7.3 KB
- references/run-code-patterns.md 7.8 KB
- references/sap-auth-cli.md 7.3 KB
- references/sap-test-generation.md 6.2 KB
- references/screenshot-patterns.md 3.1 KB
- references/table-dialog-date-cli.md 17 KB
- references/trace-cli.md 11 KB
- references/ui5-discovery-cli.md 11 KB
- references/ui5-interaction-cli.md 11 KB
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 · 602 lines · 50 tokens per session scan A 33dba7b76831
praman-sap-cli is a skill published in the GitHub repository mrkanitkar/playwright-praman (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 4,790 once invoked, about $0.0003 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 skills, from other repositories
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
playwright-trace
Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…
playwright-expert
Expert in Playwright E2E testing framework, auto-waiting mechanisms, test generation, trace viewer, and CI/CD integration. Use when the user mentions testing, end-to-end tests, QA, automation, end-to-end testing, or test automation, or when the task involves Playwright Framework, Test Organization, Advanced Features…
Playwright (Automation + MCP + Scraper)
Browser automation via Playwright MCP. Navigate websites, click elements, fill forms, take screenshots, extract data, and debug real browser workflows. Use when (1) you need a real browser, not static fetch; (2) the task involves Playwright MCP, browser tools, Playwright tests, scripts, or JS-rendered pages; (3) the…