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/nirarad/playwright-ai-qa-agent/demo-app-package-securitygit clone --depth 1 https://github.com/nirarad/playwright-ai-qa-agentWrote 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/nirarad/playwright-ai-qa-agent/demo-app-package-security)<a href="https://agentmods.dev/rules/nirarad/playwright-ai-qa-agent/demo-app-package-security"><img src="https://agentmods.dev/badge/rules/nirarad/playwright-ai-qa-agent/demo-app-package-security.svg" alt="Measured on agentmods" 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 | $0.00708 | $0.00708 |
| Opus 5 | $0.00354 | $0.00354 |
| Sonnet 5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
demo-app-package-security 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Demo App Package Security Rule
Use this rule every time demo-app/package.json is created or updated.
Goal
Keep dependency setup clean and predictable:
- No known high/critical vulnerabilities after install
- No deprecated or unnecessary packages
- Minimal warnings from install/audit commands
Required Process (Before Finalizing package.json)
- Prefer current stable packages from npm (do not invent versions).
- Keep dependencies minimal. Add only what the app actually uses.
- Separate runtime and tooling:
dependencies: only packages needed at runtimedevDependencies: TypeScript, lint, Tailwind, PostCSS, types
- Use Node 20+ compatibility for all package choices.
- Run security checks after any package change:
npm installnpm outdatednpm audit --audit-level=high
- If high/critical issues exist, update or replace the package before finalizing.
- Commit lockfile changes with package changes so installs are reproducible.
Demo-App Baseline Packages
When creating a fresh demo-app/package.json, start from this shape:
{
"name": "demo-app",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
},
"dependencies": {
"next": "LATEST_STABLE_NEXT_14",
"react": "LATEST_STABLE_REACT_18",
"react-dom": "LATEST_STABLE_REACT_18"
},
"devDependencies": {
"typescript": "LATEST_STABLE",
"@types/node": "LATEST_STABLE",
"@types/react": "LATEST_STABLE",
"@types/react-dom": "LATEST_STABLE",
"tailwindcss": "LATEST_STABLE",
"postcss": "LATEST_STABLE",
"autoprefixer": "LATEST_STABLE",
"eslint": "LATEST_STABLE_COMPATIBLE",
"eslint-config-next": "MATCH_NEXT_VERSION"
}
}
Good vs Bad
// ✅ Good: minimal, current, and purpose-separated
{
"dependencies": {
"next": "^14.2.0",
"react": "^18.2.0",
"react-dom": "^18.2.0"
},
"devDependencies": {
"typescript": "^5.6.3",
"tailwindcss": "^3.4.14"
}
}
// ❌ Bad: unused runtime deps and stale/deprecated tooling
{
"dependencies": {
"left-pad": "^1.3.0",
"moment": "^2.29.1"
},
"devDependencies": {
"eslint": "^7.0.0"
}
}
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.
- 4d ago First seen · 100 lines · 708 tokens per session scan A c1f335347d83
demo-app-package-security is a cursor rule published in the GitHub repository nirarad/playwright-ai-qa-agent (5 stars, last pushed 4mo ago), licensed MIT. It adds 708 tokens to every session, about $0.0035 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-31.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.