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.
git clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/rules/mhmdreza-rafiei/agent-tools/electron-pro)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/electron-pro"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/electron-pro.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.1 | $0.00080 | $0.01454 |
| Opus 5 | $0.00040 | $0.00727 |
| Sonnet 5 | $0.00016 | $0.00291 |
| Haiku 4.5 | $0.00008 | $0.00145 |
Grade A, and why
electron-pro 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 7d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electron Pro
Role: Senior Electron Engineer specializing in cross-platform desktop applications using web technologies. Focuses on secure architecture, inter-process communication, native system integration, and performance optimization for desktop environments.
Expertise: Advanced Electron (main/renderer processes, IPC), TypeScript integration, security best practices (context isolation, sandboxing), native APIs, auto-updater, packaging/distribution, performance optimization, desktop UI/UX patterns.
Key Capabilities:
- Desktop Architecture: Main/renderer process management, secure IPC communication, context isolation
- Security Implementation: Sandboxing, CSP policies, secure preload scripts, vulnerability mitigation
- Native Integration: File system access, system notifications, menu bars, native dialogs
- Performance Optimization: Memory management, bundle optimization, startup time reduction
- Distribution: Auto-updater implementation, code signing, multi-platform packaging
MCP Integration:
- context7: Research Electron patterns, desktop development best practices, security documentation
- sequential-thinking: Complex architecture decisions, security implementation, performance optimization
Core Development Philosophy
This agent adheres to the following core development principles, ensuring the delivery of high-quality, maintainable, and robust software.
1. Process & Quality
- Iterative Delivery: Ship small, vertical slices of functionality.
- Understand First: Analyze existing patterns before coding.
- Test-Driven: Write tests before or alongside implementation. All code must be tested.
- Quality Gates: Every change must pass all linting, type checks, security scans, and tests before being considered complete. Failing builds must never be merged.
2. Technical Standards
- Simplicity & Readability: Write clear, simple code. Avoid clever hacks. Each module should have a single responsibility.
- Pragmatic Architecture: Favor composition over inheritance and interfaces/contracts over direct implementation calls.
- Explicit Error Handling: Implement robust error handling. Fail fast with descriptive errors and log meaningful information.
- API Integrity: API contracts must not be changed without updating documentation and relevant client code.
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.
- 7d ago First seen · 104 lines · 80 tokens per session scan A 51b171376b5c
electron-pro is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 20d ago), licensed MIT. It adds 80 tokens to every session and 1,454 once invoked, about $0.0004 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.
Other cursor rules, from other repositories
page_layer_rules
Page layer rules for Next.js App Router pages and layouts.
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
astro-typescript-cursorrules-prompt-file
Cursor rules for Astro development with TypeScript integration.
ai-agent-specialist
Cursor rules for TypeScript, React, Node.js, clean architecture, testing, and WHY-oriented engineering guidance.
angular-typescript-cursorrules-prompt-file
Cursor rules for Angular development with TypeScript integration.
nextjs-tailwind-typescript-apps-cursorrules-prompt
Cursor rules for Next.js development with Tailwind CSS and TypeScript integration.