electron-mcp: Instructions file for Claude Code

CLAUDE.md

electron-mcp CLAUDE.md is an instructions file for Claude Code from YawLabs/electron-mcp. It costs 1,043 tokens per session, scanned A, original, MIT.

A set of instructions for working on an Electron MCP server. Electron is a framework for building desktop apps with web technologies, and this server helps an AI assistant work with Electron projects.

In plain words
What is it for?
Use it when developing, auditing, testing, or diagnosing the electron-mcp project, especially its IPC communication, preload bridges, security settings, content policies, and build process.
Why use it?
It gives the assistant the project's architecture, security patterns, build details, and shared analysis rules, reducing guesswork when changing or reviewing the code.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is YawLabs/electron-mcp's own configuration. It tells Claude Code how to work on electron-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything electron-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to YawLabs/electron-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/YawLabs/electron-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/YawLabs/electron-mcp

Made for: Claude Code.

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-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/yawlabs/electron-mcp/claude-md.svg)](https://agentmods.dev/instructions/yawlabs/electron-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/yawlabs/electron-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/yawlabs/electron-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,043 This file is loaded in full into every session.
When invoked 1,043 The same file — it is already loaded in full.
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.01043 $0.01043
Opus 5 $0.00522 $0.00522
Sonnet 5 $0.00209 $0.00209
Haiku 4.5 $0.00104 $0.00104

Measured 8d ago against content hash 135925983c2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

electron-mcp CLAUDE.md 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 8d 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.

CLAUDE.md · 70 lines

How it starts

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

electron-mcp

Electron.js MCP server — IPC scaffolding, security auditing, build diagnostics, and development intelligence for AI assistants.

Architecture

18 tools total, across seven tool modules plus two shared support modules.

  • src/index.ts — Entry point. Registers all tools with McpServer, appends the knowledge footer, handles version subcommand.
  • src/version.ts — Resolves the package version (esbuild __VERSION__ define, with a tsc-path package.json fallback).
  • src/knowledge.ts — Single source of truth for the embedded-knowledge vintage (KNOWLEDGE_VERSION) and the knowledgeFooter() appended to tool output.
  • src/static-analysis.ts — Shared lexical-scrub utilities (stripComments, stripCommentsAndStrings, unsafeOpenExternalCallSites) used by the analysis tools so each inherits the same comment/string handling.
  • src/tools/ipc.ts — IPC & process architecture tools (5 tools): scaffold channels, generate preload bridges, audit IPC security, window manager, process model explanation.
  • src/tools/security.ts — Security tools (4 tools): comprehensive audit, fuses config, CSP generation, security linting.
  • src/tools/build.ts — Build & distribution tools (4 tools): error diagnosis, auto-update config, deep linking, project scaffolding.
  • src/tools/migration.ts — Migration tools (2 tools): version migration checklist, deprecated API scanner. Contains embedded breaking changes database for Electron v28-v41.
  • src/tools/performance.ts — Performance tool (1 tool): detects 7 official anti-patterns.
  • src/tools/reference.ts — Reference tool (1 tool): authoritative concept explainer with 8 topics.
  • src/tools/knowledge.ts — Knowledge metadata tool (1 tool): electron_knowledge_version reports the embedded-knowledge vintage and supported version range.

Key differences from other @yawlabs MCPs

This MCP does NOT wrap a REST API. It is a development intelligence server:

  • No API key or environment variables required
  • Tools generate code and configuration rather than fetching data
  • Tools analyze code provided as input (static analysis)
  • Contains embedded Electron knowledge (breaking changes, security rules, best practices)
  • All tools are read-only — no side effects

Read the full file on GitHub · 70 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. 8d ago First seen · 70 lines · 1,043 tokens per session scan A 135925983c2f

Subscribe to this mod's changes

electron-mcp CLAUDE.md is an instructions file published in the GitHub repository YawLabs/electron-mcp (1 stars, last pushed 15d ago), licensed MIT. It adds 1,043 tokens to every session, about $0.0052 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-31.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens