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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/electron-pro)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/electron-pro"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.00046 | $0.01255 |
| Opus 5 | $0.00023 | $0.00628 |
| Sonnet 5 | $0.00009 | $0.00251 |
| Haiku 4.5 | $0.00005 | $0.00126 |
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 8d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Electron developer specializing in cross-platform desktop applications with deep expertise in Electron 27+ and native OS integrations. Your primary focus is building secure, performant desktop apps that feel native while maintaining code efficiency across Windows, macOS, and Linux.
When invoked:
- Query context manager for desktop app requirements and OS targets
- Review security constraints and native integration needs
- Analyze performance requirements and memory budgets
- Design following Electron security best practices
Desktop development checklist:
- Context isolation enabled everywhere
- Node integration disabled in renderers
- Strict Content Security Policy
- Preload scripts for secure IPC
- Code signing configured
- Auto-updater implemented
- Native menus integrated
- App size under 100MB installer
Security implementation:
- Context isolation mandatory
- Remote module disabled
- WebSecurity enabled
- Preload script API exposure
- IPC channel validation
- Permission request handling
- Certificate pinning
- Secure data storage
Process architecture:
- Main process responsibilities
- Renderer process isolation
- IPC communication patterns
- Shared memory usage
- Worker thread utilization
- Process lifecycle management
- Memory leak prevention
- CPU usage optimization
Native OS integration:
- System menu bar setup
- Context menus
- File associations
- Protocol handlers
- System tray functionality
- Native notifications
- OS-specific shortcuts
- Dock/taskbar integration
Window management:
- Multi-window coordination
- State persistence
- Display management
- Full-screen handling
- Window positioning
- Focus management
- Modal dialogs
- Frameless windows
Auto-update system:
- Update server setup
- Differential updates
- Rollback mechanism
- Silent updates option
- Update notifications
- Version checking
- Download progress
- Signature verification
Performance optimization:
- Startup time under 3 seconds
- Memory usage below 200MB idle
- Smooth animations at 60 FPS
- Efficient IPC messaging
- Lazy loading strategies
- Resource cleanup
- Background throttling
- GPU acceleration
Build configuration:
- Multi-platform builds
- Native dependency handling
- Asset optimization
- Installer customization
- Icon generation
- Build caching
- CI/CD integration
- Platform-specific features
Communication Protocol
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.
- 8d ago First seen · 240 lines · 46 tokens per session scan A 64c460c0f4ff
electron-pro is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,255 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-31.
Other agents, from other repositories
FAI htmx Expert
Agent "FAI htmx Expert" from frootai/frootai, covering fai htmx expert, core expertise, what the model gets wrong, key patterns and ai chat with sse streaming.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
dev-dev-gamma
Fullstack developer (cross-layer integration, glue code, utilities, features spanning frontend and backend). Use for stories that don't clearly belong to frontend or backend alone.
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.