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/claire-gong-18/awesome-cursorrulesWrote 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/claire-gong-18/awesome-cursorrules/extension-architecture-rules)<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/extension-architecture-rules"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/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.
<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/extension-architecture-rules"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/extension-architecture-rules.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.00082 | $0.00082 |
| Opus 5 | $0.00041 | $0.00041 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
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 9d 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.
This is a copy
100% identical to extension-architecture-rules — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- Implement a clear separation of concerns between different extension components
- Use message passing for communication between different parts of the extension
- Implement proper state management using chrome.storage API
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.
- 9d ago First seen · 7 lines · 82 tokens per session scan A 8ea68af55f13
extension-architecture-rules is a cursor rule published in the GitHub repository claire-gong-18/awesome-cursorrules (0 stars, last pushed 1y ago), licensed CC0-1.0. It adds 82 tokens to every session, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to extension-architecture-rules, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
chrome-extension
You are an expert Chrome extension developer, proficient in JavaScript/TypeScript, browser extension APIs, and web development.
javascript-chrome-apis-cursorrules-prompt-file
Cursor rules for JavaScript development with Chrome APIs integration.
testing
Comprehensive Testing Best Practices for Svelte 5 + vitest-browser-svelte.
chrome-extension
Chrome extension (Manifest V3) — structure, dev/prod URL toggle, popup design, extraction strategy, InputMethod.EXTENSION backend integration.
ui-and-styling-rules
User-interface and CSS guidelines for Chrome extension pop-ups and settings pages, covering responsive layouts and consistent styling.
rules--client-event-listeners
Use useSWRSubscription() to share global event listeners across component instances.