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/paulpham157/paul-s-cursor-rules/browser-api-usage-rulesgit clone --depth 1 https://github.com/paulpham157/paul-s-cursor-rulesWhat 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.00072 |
| Opus 5 | $0.00000 | $0.00036 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
browser-api-usage-rules 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 3d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- browser-api-usage-rules — 100% identical, 0 lines differ
- browser-api-usage-rules — 100% identical, 0 lines differ
What it actually says
- Utilize chrome.* APIs effectively (e.g., chrome.tabs, chrome.storage, chrome.runtime)
- Implement proper error handling for all API calls
- Use chrome.alarms for scheduling tasks instead of setInterval
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.
- 3d ago First seen · 7 lines · 72 tokens per session scan A 6644fdc50335
browser-api-usage-rules is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 72 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
chrome-extension-dev-js-typescript-cursorrules-pro
Cursor rules for VSCode extension development with Electron and TypeScript integration.
ankra-cli
Ankra CLI rules and best practices for managing Kubernetes clusters via the Ankra platform.
code-style-consistency-cursorrules-prompt-file
Cursor rules for code development with style consistency integration.
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.
cypress-api-testing-cursorrules-prompt-file
Cursor rules for Cypress development with API testing.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.