extension-architecture-rules

extension-architecture-rules is a cursor rule for Cursor from holtwood/awesome-cursorrules-zh. It costs 0 tokens per session (91 once invoked), scanned A, original, MIT.

Architecture guidelines for Chrome extensions that separate each part of the extension and let those parts communicate through messages and shared storage.

In plain words
What is it for?
Use them when structuring extension components, defining message passing, or storing extension state with chrome.storage.
Why use it?
They help prevent unrelated responsibilities from becoming tangled and provide a consistent way to manage state between extension components.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use them when structuring extension components, defining message passing, or storing extension state with chrome.storage.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/holtwood/awesome-cursorrules-zh/extension-architecture-rules
Install

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.

Clone the repo
git clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zh

Made for: Cursor.

Wrote 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.

agentmods badge for extension-architecture-rules

README.md
[![agentmods](https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/extension-architecture-rules/github.svg)](https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/extension-architecture-rules)
Your own site
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/extension-architecture-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/extension-architecture-rules/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.

agentmods 80×15 button for extension-architecture-rules

Your own site · 80×15
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/extension-architecture-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/extension-architecture-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 91 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00091
Opus 5 $0.00000 $0.00046
Sonnet 5 $0.00000 $0.00018
Haiku 4.5 $0.00000 $0.00009

Measured 6d ago against content hash b0edfd3f42fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

extension-architecture-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 6d 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.

docs/rules/frontend/chrome/chrome-extension-dev-js-typescript/extension-architecture-rules.mdc · 8 lines

What it actually says

  • 实现清晰的关注点分离,区分不同扩展组件
  • 使用消息传递实现不同部分间的通信
  • 使用 chrome.storage API 实现适当的状态管理
Changes

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.

  1. 6d ago First seen · 8 lines · 91 tokens per session scan A b0edfd3f42fd

Subscribe to this mod's changes

extension-architecture-rules is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (233 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 91 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.