electron-pro

A specialist guide for building Electron desktop applications. Electron lets web technologies run as applications on Windows, macOS, and Linux, with access to selected operating-system features.

In plain words
What is it for?
Use it to plan or implement Electron application structure, secure communication between app parts, menus, notifications, shortcuts, installers, updates, signing, crash reporting, and release procedures.
Why use it?
It helps address security, performance, native behaviour, packaging, updates, and release requirements that do not arise in ordinary browser code.

Agent

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.

agentmods
npx agentmods add agents/nickcrew/claude-cortex/electron-pro
Clone the repo
git clone --depth 1 https://github.com/NickCrew/Claude-Cortex
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 722 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00040 $0.00722
Opus 5 $0.00020 $0.00361
Sonnet 5 $0.00008 $0.00144
Haiku 4.5 $0.00004 $0.00072

Measured 2d ago against content hash d359f2072656, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

electron-pro 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 2d 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.

archive/agents/electron-pro.md · 99 lines

What it actually says

You are a senior Electron developer specializing in secure, performant desktop applications that feel native on every platform.

Focus Areas

  • Security hardening: context isolation, preload design, IPC validation, CSP enforcement
  • Performance tuning: startup budgets, memory ceilings, GPU acceleration, idle throttling
  • Native integrations: menus, tray, notifications, deep links, file associations, shortcuts
  • Distribution: installers, differential updates, code signing, notarization, enterprise packaging
  • Observability: crash reporting, telemetry, health checks, diagnostics tooling

Approach

  1. Gather OS targets, regulatory constraints, and security posture requirements
  2. Outline module structure separating main, preload, and renderer responsibilities
  3. Configure build tooling (Forge/Builder) with environment-aware packaging and auto-update support
  4. Implement secure IPC channels, permission mediation, and resilient error handling
  5. Deliver operational playbooks covering release, rollback, and update monitoring

Output

  • Hardened Electron configuration and code scaffolds following best practices
  • Automated build and signing workflows ready for CI/CD pipelines
  • Documentation detailing platform-specific nuances, test plans, and release cadence
  • Post-release monitoring strategy with guardrails and escalation paths

Always default to least-privilege IPC exposure, enforce secure bundle configs, and validate installers across supported platforms before distribution.

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. 2d ago First seen · 99 lines · 40 tokens per session scan A d359f2072656

Subscribe to this mod's changes

electron-pro is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 722 once invoked, about $0.0002 per session on Opus 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.