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 skills add ersinkoc/security-check --skill sc-local-ipcgit clone --depth 1 https://github.com/ersinkoc/security-checkWrote 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/skills/ersinkoc/security-check/sc-local-ipc)<a href="https://agentmods.dev/skills/ersinkoc/security-check/sc-local-ipc"><img src="https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-local-ipc/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.
<a href="https://agentmods.dev/skills/ersinkoc/security-check/sc-local-ipc"><img src="https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-local-ipc.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00023 | $0.02086 |
| Opus 5.5 | $0.00009 | $0.00834 |
| Sonnet 5.5 | $0.00005 | $0.00417 |
| Haiku 4.5 | $0.00002 | $0.00209 |
Grade A, and why
sc-local-ipc 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SC: Desktop, Mobile, and Local IPC Security
Purpose
Find boundary failures between remote content, local applications, operating-system users, sandboxed processes, native UI, local daemons, and privileged helpers. A local path, process name, claimed sender, package name, or loopback address is not peer authentication.
Activation
Run for Electron, Tauri, native desktop or mobile apps, webview hosts, custom URL schemes, app links, exported mobile components, browser native-messaging hosts, Unix sockets, named pipes, XPC, Binder, D-Bus, loopback RPC, privileged helpers, installers, updaters, or local daemons.
Phase 1: Discovery
Principal and channel map
Enumerate every process, app component, local endpoint, URI scheme, file association, webview origin, helper, installer, and updater. Record:
- realistic caller: remote origin, untrusted file, sandboxed child, another app, another OS user, or lower-privilege account;
- process identity, OS user, sandbox, integrity level, entitlements, and runtime privilege;
- channel creation, ownership, ACL, namespace, and peer-credential mechanism;
- callable operations and selected resources;
- per-operation authorization, confirmation, and current-session binding.
Packaging and lifecycle
Read source-controlled manifests, entitlements, installer rules, native-messaging registrations, protocol handlers, service definitions, ACL creation, and update configuration. Note where final signing, merged manifests, installed ACLs, device policy, or OS-version behavior is not visible.
Native bridge and file paths
Trace every webview/native bridge, IPC dispatcher, file-open handler, drag/drop entry, clipboard/pasteboard read, notification action, shared-memory region, temp file, and privileged file operation to its final sink.
Phase 2: Vulnerability Hunting
Deep links and handoffs
- Custom schemes or deep links mutate state, import data, select accounts, or complete authentication without a one-time current-session binding.
- OAuth, SSO, magic links, invites, pairing, or payment callbacks can return to the wrong installed app, profile, tenant, provider, or pending transaction.
- Duplicate parameters, URI normalization, ambiguous host/path matching, stale links, or replay change the selected operation.
- File-open, share, notification, or clipboard content triggers privileged behavior without binding to current user intent.
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.
- 1mo ago First seen · 154 lines · 23 tokens per session scan A 823277fd8c58
sc-local-ipc is a skill published in the GitHub repository ersinkoc/security-check (83 stars, last pushed 17d ago), licensed MIT. It adds 23 tokens to every session and 2,086 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-09-16.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…