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/zeyadelosherey/tapwisper-desktop/electron-patternsgit clone --depth 1 https://github.com/zeyadelosherey/tapwisper-desktopWrote 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/zeyadelosherey/tapwisper-desktop/electron-patterns)<a href="https://agentmods.dev/rules/zeyadelosherey/tapwisper-desktop/electron-patterns"><img src="https://agentmods.dev/badge/rules/zeyadelosherey/tapwisper-desktop/electron-patterns.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00518 |
| Opus 5 | $0.00000 | $0.00259 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
electron-patterns 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 5d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electron Main Process Patterns
Window Management
- Windows are created in
src/main/windows.ts - Overlay windows (recording pill, pinned panel, command popup, AI panel) are pre-warmed at startup
- Each overlay loads the same renderer entry point but with a different hash route
- Main window is 1000x700 and resizable; overlays are small, frameless, and always-on-top
IPC Communication
- IPC handlers are registered in
src/main/ipc-handlers.ts - Use
ipcMain.handle()for async request/response patterns - Use
ipcMain.on()for fire-and-forget events - Send events to renderer via
webContents.send() - The preload script (
src/preload/index.ts) exposes all IPC methods aswindow.tapwisper.*
Global Shortcuts
- Keyboard shortcuts use
uiohook-napi(not Electron's globalShortcut) - Shortcut logic lives in
src/main/shortcuts.ts - Key constants (hold threshold, grace period, cooldown) are in
src/main/constants.ts
Data Storage
- Config:
electron-storefor user settings (API keys, preferences) - Database:
better-sqlite3for activity tracking and stats (src/main/database.ts) - Migrations: Data migration utilities in
src/main/migrate-data.ts
Security
- Context isolation is enabled -- renderer cannot access Node.js APIs directly
- All renderer-to-main communication must go through the preload contextBridge
- Never expose raw
ipcRendererto the renderer process - API keys are stored via electron-store (encrypted at rest)
Audio
- Audio recording and encoding logic is in
src/main/audio.ts - Audio blobs are passed to the renderer for transcription via AI providers
Permissions
- Platform-aware permission checking and requesting lives in
src/main/permissions.ts - macOS: checks microphone (
systemPreferences.getMediaAccessStatus), accessibility (isTrustedAccessibilityClient), and screen recording - Windows/Linux: only microphone is relevant; accessibility and screen recording are always reported as
'granted' - IPC handlers:
permissions:checkreturns all statuses,permissions:requesttriggers the native prompt or opens system settings - Exposed to renderer via
window.tapwisper.permissions.check()andwindow.tapwisper.permissions.request(type)
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.
- 5d ago First seen · 55 lines · 0 tokens per session scan A 3bb966b2132a
electron-patterns is a cursor rule published in the GitHub repository zeyadelosherey/tapwisper-desktop (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 518 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.