auditing-electron-ipc-trust

auditing-electron-ipc-trust is a skill for Claude Code from UnboundCompute/security-agent-skills. It costs 189 tokens per session (2,120 once invoked), scanned A, original, MIT.

A security review guide for Electron desktop apps, which combine web pages with access to the computer. It examines whether untrusted page content can reach Node.js or operating-system functions through the app’s bridge and message handlers.

In plain words
What is it for?
Use it to review window settings, preload scripts, exposed bridges, message handlers, and native calls after resolving isolation and sandbox settings.
Why use it?
It helps find paths where a browser-side bug or injected content could become code execution.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the security-agent-skills plugin — 194 skills shipped together

Good fit Use it to review window settings, preload scripts, exposed bridges, message handlers, and native calls after resolving isolation and sandbox settings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/unboundcompute/security-agent-skills/auditing-electron-ipc-trust
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.

Any agent
npx skills add UnboundCompute/security-agent-skills --skill auditing-electron-ipc-trust
Clone the repo
git clone --depth 1 https://github.com/UnboundCompute/security-agent-skills

Made for: Claude Code.

Or install security-agent-skills, the plugin that ships this one along with the rest of its 194 skills.

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 auditing-electron-ipc-trust

README.md
[![agentmods](https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-electron-ipc-trust/github.svg)](https://agentmods.dev/skills/unboundcompute/security-agent-skills/auditing-electron-ipc-trust)
Your own site
<a href="https://agentmods.dev/skills/unboundcompute/security-agent-skills/auditing-electron-ipc-trust"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-electron-ipc-trust/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 auditing-electron-ipc-trust

Your own site · 80×15
<a href="https://agentmods.dev/skills/unboundcompute/security-agent-skills/auditing-electron-ipc-trust"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-electron-ipc-trust.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 189 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,120 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00189 $0.02120
Opus 5 $0.00095 $0.01060
Sonnet 5 $0.00038 $0.00424
Haiku 4.5 $0.00019 $0.00212

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

Security

Grade A, and why

auditing-electron-ipc-trust scanned grade A with 1 finding 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 12d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

> page for a live feature. A cross-site-scripting in that page runs `require('child_process').exec` with an
skills/auditing-electron-ipc-trust/SKILL.md · 142 lines

How it starts

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

Auditing Electron IPC trust: when renderer content reaches a native capability

An Electron app is dangerous where content in a renderer, whether remote, injected through a cross-site-scripting, or arriving over a custom protocol, reaches a Node or operating-system capability. The marquee chain is a renderer bug escalating to code execution because the renderer can require Node directly, or because the preload bridge hands untrusted input to a native call. You audit it by resolving, per native sink, whether context isolation and the sandbox stand between the renderer and Node and whether the preload and IPC surface validate what they pass. The single most important false-positive killer is that context isolation and the sandbox being on make an otherwise alarming exposed symbol harmless, so resolve those two settings before judging any bridge. Renderer-side markup injection itself belongs to the client-side DOM skill; this skill owns the bridge and the IPC substrate.

When to use

  • You are reviewing an Electron app's window configuration, its preload scripts, and its IPC handlers.
  • You see webPreferences, a contextBridge exposure, an ipcMain handler, or a loadURL or openExternal call.
  • You want to know whether untrusted renderer content can reach a Node or operating-system capability.

Scope check

Audit only apps you own or are authorized to assess, and drive a renderer-to-main path only against a build in scope, an IPC handler that reaches a shell or the filesystem acts on your host. Adjudicate on the window configuration and the handlers. If you can't name the authorization, stop.

The loop

  1. Resolve context isolation and the sandbox first. Read the webPreferences for each window: is nodeIntegration off, is contextIsolation on, is the sandbox on. These settings decide whether the renderer can reach Node at all, so an exposed require or a Node symbol is only exploitable when they are off. Settle them before judging any exposed surface, because they are the killer for most leads.

Read the full file on GitHub · 142 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. 12d ago First seen · 142 lines · 189 tokens per session scan A a1bbbb46d940

Subscribe to this mod's changes

auditing-electron-ipc-trust is a skill published in the GitHub repository UnboundCompute/security-agent-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 189 tokens to every session and 2,120 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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

prodcheck-review

Review this codebase against the prodcheck pre-production checklists — security, performance, scale, integrations and post-launch readiness. Use when asked to check whether a project is ready to ship, to audit an area before launch, or to work through a specific checklist. Produces evidence with file:line citations…

FarzamHabibi/pre-production-checklist · 70 tokens

integrate-arcjet-guard-genkit

Integrate Arcjet security into a Genkit JS agent using @arcjet/guard — wrap ai.defineTool, put guardMiddleware on generate({ use }) for unwrapped / MCP / filesystem tools, and read a caller-owned id from generate({ context }). Use when asked to add Arcjet to genkit, rate limit its tools, screen inbound messages, or…

arcjet/arcjet-js · 89 tokens

integrate-arcjet-guard-langgraph

Integrate Arcjet security into a LangGraph Graph API agent using @arcjet/guard — wrap tool() / StructuredTool, wrap ToolNode for unwrapped MCP tools, and read threadid for correlation. Use when asked to add Arcjet to a LangGraph StateGraph / ToolNode agent, rate limit its tools, screen inbound messages, or block…

arcjet/arcjet-js · 87 tokens

integrate-arcjet-guard-tanstack-ai

Integrate Arcjet security into a TanStack AI chat() app using @arcjet/guard — put guardMiddleware first on chat({ middleware }) so onBeforeToolCall gates tools, and read a caller-owned id from chat({ context }). Use when asked to add Arcjet to TanStack AI, rate limit its tools, screen inbound messages, or block prompt…

arcjet/arcjet-js · 103 tokens

integrate-arcjet-guard-claude-managed-agents

Integrate Arcjet security into Claude Managed Agents (hosted REST+SSE, beta managed-agents-2026-04-01) using @arcjet/guard — screen user.message / initialevents before sessions.events.send, and gate custom tools on agent.customtooluse. Use when asked to add Arcjet to Claude Managed Agents, rate limit custom tools, or…

arcjet/arcjet-js · 102 tokens

linear-claude-skill

Manage Linear issues, projects, and teams.

Agent-Threat-Rule/agent-threat-rules · 15 tokens