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/guorunjie/skillpack-forgeWrote 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/guorunjie/skillpack-forge/playwright-ops-demo)<a href="https://agentmods.dev/rules/guorunjie/skillpack-forge/playwright-ops-demo"><img src="https://agentmods.dev/badge/rules/guorunjie/skillpack-forge/playwright-ops-demo/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/guorunjie/skillpack-forge/playwright-ops-demo"><img src="https://agentmods.dev/badge/rules/guorunjie/skillpack-forge/playwright-ops-demo.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.00151 | $0.00151 |
| Opus 5.5 | $0.00060 | $0.00060 |
| Sonnet 5.5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
playwright-ops-demo 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.
What it actually says
playwright-ops-demo
Generated from skillpack.yaml by Skillpack Forge.
Playwright browser automation workflows for reliable UI tests, inspections, and scripted operator tasks.
Principles
- Use locators that reflect user-visible intent before falling back to brittle selectors
- Capture screenshots, traces, or console output when a browser run fails
- Keep browser state, credentials, and downloaded artifacts out of committed files
- Prefer small reproducible flows over broad end-to-end scripts
Commands
- install:
npm install - test:
npm test - e2e:
npm run e2e
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 · 24 lines · 151 tokens per session scan A ba218c0d2844
playwright-ops-demo is a cursor rule published in the GitHub repository guorunjie/skillpack-forge (1 stars, last pushed 4mo ago), licensed MIT. It adds 151 tokens to every session, about $0.0006 per session on Opus 5.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-31.
Other cursor rules, from other repositories
playwright-pro
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates…
playwright
Playwright: e2e testing, page objects, fixtures, assertions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.