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/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/electron)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/electron"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/electron/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/nedcodes-ok/cursorrules-collection/electron"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/electron.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.00482 | $0.00482 |
| Opus 5.5 | $0.00193 | $0.00193 |
| Sonnet 5.5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
electron 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electron Cursor Rules
You are an expert Electron developer. Follow these rules:
Architecture
- Strict main/renderer process separation. Never import electron in renderer directly
- Preload scripts as the ONLY bridge between main and renderer
- Use contextBridge.exposeInMainWorld() to expose typed APIs to renderer
- Renderer process is a web app — treat it like a browser environment
IPC Communication
- Use ipcMain.handle/ipcRenderer.invoke for request-response (async, returns promise)
- Use ipcMain.on/webContents.send for main-to-renderer push events
- Define all IPC channels as string constants in a shared channels.ts file
- Type all IPC messages: define interfaces for every channel's payload and response
- Never use ipcRenderer.sendSync — it blocks the renderer process
Security
- Enable contextIsolation: true and sandbox: true on all BrowserWindows
- Set nodeIntegration: false. Always. No exceptions
- Validate all IPC inputs in main process — renderer is untrusted
- Use safeStorage for encrypting sensitive data at rest
- Set webPreferences.webSecurity: true. Never disable for CORS workarounds
- CSP headers on all loaded pages. No unsafe-eval, no unsafe-inline
Windows & Views
- BrowserWindow for top-level windows. BrowserView or WebContentsView for embedded content
- Save/restore window bounds with electron-store or custom persistence
- Use win.webContents.setWindowOpenHandler() to control popup behavior
- Show window after ready-to-show event to avoid white flash
File System & Native
- Use app.getPath() for platform-correct directories (userData, documents, temp)
- dialog.showOpenDialog/showSaveDialog for file operations — never custom file pickers
- Use shell.openExternal() for URLs, shell.openPath() for files — validate URLs first
- Native menus via Menu.buildFromTemplate(). Platform-specific roles (undo, copy, paste)
Updates & Distribution
- electron-updater with auto-update support. Check on startup + periodic interval
- Code sign for macOS and Windows. Notarize for macOS
- Use electron-builder or electron-forge for packaging
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 · 48 lines · 482 tokens per session scan A a084f66654c4
electron is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (38 stars, last pushed 7mo ago), licensed MIT. It adds 482 tokens to every session, about $0.0019 per session on Opus 5.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-30.
Other cursor rules, from other repositories
auto-update-llms-robots-txt
Auto-update llms.txt and robots.txt when pages are created or edited.
10-feature-development
Feature implementation workflow and engineering mindset.
11-template-conventions
Reusable building blocks shipped with this template - use them instead of writing new ones.
03-ui
UI, layout, theming and localization standards.
09-android-best-practices
Android engineering best practices.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.