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 antropos17/Aegis --skill electron-maingit clone --depth 1 https://github.com/antropos17/AegisWrote 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/antropos17/aegis/electron-main)<a href="https://agentmods.dev/skills/antropos17/aegis/electron-main"><img src="https://agentmods.dev/badge/skills/antropos17/aegis/electron-main/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/antropos17/aegis/electron-main"><img src="https://agentmods.dev/badge/skills/antropos17/aegis/electron-main.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.00026 | $0.00313 |
| Opus 5.5 | $0.00010 | $0.00125 |
| Sonnet 5.5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
electron-main 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 today.
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.
What it actually says
Electron main process
Main modules use CommonJS and JavaScript with JSDoc. Follow AGENTS.md and inspect effective TypeScript settings before claiming body-level type coverage. Derive dependency versions from package.json.
- Route OS-specific operations through src/main/platform/index.js and the matching platform module.
- Check both the main handler and src/main/preload.js when changing IPC contracts; retain channel/input validation and the narrow contextBridge surface.
- Read scan-loop.js for staggered startup, scan intervals and shutdown cleanup. Those are separate scheduling mechanisms; preserve their lifecycle instead of copying fixed delays into new code.
- Read ipc-batcher.js and its callers for flush mode, capacity and timing. The stats-update caller uses latest-value batching: a pending flush timer is not restarted on every event. Do not replace it with trailing debounce that can postpone delivery indefinitely.
- Follow each chokidar watcher's actual ignored predicate and path semantics in file-watcher.js; the installed library accepting globs does not make a glob equivalent to that predicate.
- Reuse existing init(deps), _setDepsForTest() and _resetForTest() seams where present. Preserve stamped identity and outage invariants from CODING_STANDARDS.md when changing monitoring behavior.
Keep watched secret contents and provider credentials out of logs, IPC payloads and exports. Verify the affected behavior with focused tests and the required project checks.
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.
- today First seen · 18 lines · 26 tokens per session scan A 0f01468cc8e4
electron-main is a skill published in the GitHub repository antropos17/Aegis (157 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 313 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-10-17.
Other skills, from other repositories
eac-desktop-tips
A quick reference for using and troubleshooting features in the Deepseek Harness EAC desktop client. It covers window behavior, conversation rollback, plugins, desktop pets, Skills, MCP services, updates, and logs.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
acr-agent-registry
Behavioral registry for AI agents. Log interactions, build an interaction profile, query it through lenses (friction, coverage, stable corridors, failure registry, trend), and receive anomaly signal notifications if ACR observes elevated signals on a component in your composition.
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
generate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
create-canvas
Create a project Copilot extension canvas for the current workspace.