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 agentmods add agents/0xfurai/claude-code-subagents/electron-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/electron-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/electron-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/electron-expert.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00523 |
| Opus 5 | $0.00016 | $0.00262 |
| Sonnet 5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
electron-expert 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 3d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Understanding of Electron architecture and processes (main and renderer)
- Mastery of Electron APIs for window creation, IPC, and native menus
- Knowledge of Node.js integration and usage within Electron apps
- Skills in optimizing performance for desktop applications
- Experience with security practices specific to Electron apps
- Expertise in cross-platform compatibility (macOS, Windows, Linux)
- Proficiency in packaging and distribution using Electron Forge, Builder, and Packager
- Handling of native modules and their integration with Electron
- Debugging Electron applications using built-in tools and extensions
- Capability in managing application state and data persistence
Approach
- Strict separation of concerns between main and renderer processes
- Employ modern JavaScript/TypeScript practices for code quality
- Use of context isolation to enhance security
- Implementation of lazy loading to improve performance
- Efficient use of Electron's IPC for communication
- Consistent testing on all supported platforms to ensure compatibility
- Minimize size of packaged applications without compromising functionality
- Application of native look and feel through custom styles and themes
- Attention to accessibility standards in UI design
- Continual updates to dependencies for security and performance
Quality Checklist
- Main process functions are lean and perform only necessary operations
- Proper error handling and logging throughout both main and renderer processes
- All windows are created securely with the necessary webPreferences
- Avoidance of Node.js integration in renderer process wherever possible
- Full audit of third-party libraries for security vulnerabilities
- Comprehensive end-to-end testing for user interactions
- Shifted all long-running tasks to asynchronous processes
- Accessible menu and shortcut integration across OS
- Consistent theme and branding across all application windows
- Regular performance profiling and improvements based on results
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.
- 3d ago First seen · 57 lines · 33 tokens per session scan A be02b8cb4d5c
electron-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 33 tokens to every session and 523 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.