electron-development

electron-development is a skill for Claude Code, Codex from AI-Safeter/antigravity-cli-plugin. It costs 33 tokens per session (6,762 once invoked), scanned A, original, MIT.

A guide for building and securing Electron desktop applications. Electron is a framework for making desktop apps with web technologies such as JavaScript, HTML, and CSS.

In plain words
What is it for?
Use it when creating, securing, debugging, packaging, distributing, or updating an Electron desktop app.
Why use it?
It helps structure communication between app processes and handle security, packaging, signing, updates, and native operating-system features.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is preload: path.join(__dirname, '../preload/preload.js'),.

Good fit Use it when creating, securing, debugging, packaging, distributing, or updating an Electron desktop app.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/AI-Safeter/antigravity-cli-plugin
agentmods
npx agentmods add skills/ai-safeter/antigravity-cli-plugin/electron-development

Made for: Claude Code, Codex.

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 electron-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/ai-safeter/antigravity-cli-plugin/electron-development/github.svg)](https://agentmods.dev/skills/ai-safeter/antigravity-cli-plugin/electron-development)
Your own site
<a href="https://agentmods.dev/skills/ai-safeter/antigravity-cli-plugin/electron-development"><img src="https://agentmods.dev/badge/skills/ai-safeter/antigravity-cli-plugin/electron-development/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 electron-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/ai-safeter/antigravity-cli-plugin/electron-development"><img src="https://agentmods.dev/badge/skills/ai-safeter/antigravity-cli-plugin/electron-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,762 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.00033 $0.06762
Opus 5.5 $0.00013 $0.02705
Sonnet 5.5 $0.00007 $0.01352
Haiku 4.5 $0.00003 $0.00676

Measured 1mo ago against content hash 86e566a3592c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

electron-development 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/electron-development/SKILL.md · 857 lines

How it starts

The opening of the file, as written. The whole thing — 857 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Electron Development

You are a senior Electron engineer specializing in secure, production-grade desktop application architecture. You have deep expertise in Electron's multi-process model, IPC security patterns, native OS integration, application packaging, code signing, and auto-update strategies.

Use this skill when

  • Building new Electron desktop applications from scratch
  • Securing an Electron app (contextIsolation, sandbox, CSP, nodeIntegration)
  • Setting up IPC communication between main, renderer, and preload processes
  • Packaging and distributing Electron apps with electron-builder or electron-forge
  • Implementing auto-update with electron-updater
  • Debugging main process issues or renderer crashes
  • Managing multiple windows and application lifecycle
  • Integrating native OS features (menus, tray, notifications, file system dialogs)
  • Optimizing Electron app performance and bundle size

Do not use this skill when

  • Building web-only applications without desktop distribution → use react-patterns, nextjs-best-practices
  • Building Tauri apps (Rust-based desktop alternative) → use tauri-development if available
  • Building Chrome extensions → use chrome-extension-developer
  • Implementing deep backend/server logic → use nodejs-backend-patterns
  • Building mobile apps → use react-native-architecture or flutter-expert

Instructions

  1. Analyze the project structure and identify process boundaries.
  2. Enforce security defaults: contextIsolation: true, nodeIntegration: false, sandbox: true.
  3. Design IPC channels with explicit whitelisting in the preload script.
  4. Implement, test, and build with appropriate tooling.
  5. Validate against the Production Security Checklist before shipping.

Core Expertise Areas

1. Project Structure & Architecture

Recommended project layout:

my-electron-app/
├── package.json
├── electron-builder.yml        # or forge.config.ts
├── src/
│   ├── main/
│   │   ├── main.ts             # Main process entry
│   │   ├── ipc-handlers.ts     # IPC channel handlers
│   │   ├── menu.ts             # Application menu
│   │   ├── tray.ts             # System tray
│   │   └── updater.ts          # Auto-update logic
│   ├── preload/
│   │   └── preload.ts          # Bridge between main ↔ renderer
│   ├── renderer/
│   │   ├── index.html          # Entry HTML
│   │   ├── App.tsx             # UI root (React/Vue/Svelte/vanilla)
│   │   ├── components/
│   │   └── styles/
│   └── shared/
│       ├── constants.ts        # IPC channel names, shared enums
│       └── types.ts            # Shared TypeScript interfaces
├── resources/
│   ├── icon.png                # App icon (1024x1024)
│   └── entitlements.mac.plist  # macOS entitlements
├── tests/
│   ├── unit/
│   └── e2e/
└── tsconfig.json

Read the full file on GitHub · 857 lines

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. 1mo ago First seen · 857 lines · 33 tokens per session scan A 86e566a3592c

Subscribe to this mod's changes

electron-development is a skill published in the GitHub repository AI-Safeter/antigravity-cli-plugin (10 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 6,762 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens