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/paulpham157/paul-s-cursor-rulesWrote 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/paulpham157/paul-s-cursor-rules/extension-architecture-guidelines)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/extension-architecture-guidelines"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/extension-architecture-guidelines/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/paulpham157/paul-s-cursor-rules/extension-architecture-guidelines"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/extension-architecture-guidelines.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.00000 | $0.00036 |
| Opus 5.5 | $0.00000 | $0.00014 |
| Sonnet 5.5 | $0.00000 | $0.00007 |
| Haiku 4.5 | $0.00000 | $0.00004 |
Grade A, and why
extension-architecture-guidelines 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- extension-architecture-guidelines — 100% identical, 0 lines differ
What it actually says
description: Guidelines for structuring the architecture of a Chrome extension, focusing on modularity and maintainability. globs: **/*.{js,html}
- Extension Architecture
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 · 5 lines · 36 tokens per session scan A ac1d38bb7f25
extension-architecture-guidelines 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 36 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-09-03.
Other cursor rules, from other repositories
chrome-extension-dev-js-typescript-cursorrules-pro
Cursor rules for VSCode extension development with Electron and TypeScript integration.
javascript-chrome-apis-cursorrules-prompt-file
Cursor rules for JavaScript development with Chrome APIs integration.
chrome-extension-general-rules
General Chrome extension rules guide architecture, security, performance, and integration with an existing project. They cover JavaScript, TypeScript, HTML, CSS, browser APIs, and several interface libraries.
extension-architecture-rules
Architecture guidelines for Chrome extensions that separate each part of the extension and let those parts communicate through messages and shared storage.
typescript-usage-rules
TypeScript guidelines for defining data shapes with interfaces and checking different possible values with union types and type guards.
browser-api-usage-rules
Chrome browser API rules cover browser extension interfaces such as tabs, storage, and runtime. They require error handling and recommend Chrome alarms for scheduled work instead of setInterval.