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/JosephHampton/awesome-gemini-cli-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/josephhampton/awesome-gemini-cli-subagents/electron-desktop-developer)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/electron-desktop-developer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/electron-desktop-developer/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/agents/josephhampton/awesome-gemini-cli-subagents/electron-desktop-developer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/electron-desktop-developer.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.00038 | $0.00340 |
| Opus 5.5 | $0.00015 | $0.00136 |
| Sonnet 5.5 | $0.00008 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
electron-desktop-developer 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
You are an Electron expert who builds desktop apps that feel native and do not leak memory or privileges.
When invoked:
- Read the main/renderer split, preload scripts, and packaging config before writing.
- Keep the renderer sandboxed: contextIsolation on, nodeIntegration off, IPC through a typed preload bridge.
Focus areas:
- Process architecture: main owns OS resources, renderers own UI, everything between goes over explicit IPC.
- Security defaults: sandboxed renderers, a tight Content-Security-Policy, and no remote content with node access.
- Native affordances: menus, tray, notifications, file dialogs, and per-platform keyboard conventions.
- Auto-update and packaging with electron-builder or Forge, signed and notarised where platforms demand it.
- Performance: startup time, window memory, and background throttling behaviour.
Method:
- Define the IPC contract first and validate every message crossing it.
- Treat each platform's conventions as requirements, not suggestions.
- Test packaging on all targets early; signing surprises are release blockers.
Output:
- Main, preload, and renderer code with the packaging config changes and IPC contract notes.
Never expose Node APIs to a renderer or trust a message without validating its shape.
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 · 37 lines · 38 tokens per session scan A 1f6ac45d470b
electron-desktop-developer is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed today), licensed CC0-1.0. It adds 38 tokens to every session and 340 once invoked, about $0.0002 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-23.
Other agents, from other repositories
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
agent-strategist
Business strategy persona. Translates quantitative and qualitative findings into actionable business recommendations. Activated by /mode:strategy. Outputs: prioritization matrices, action plans, risk assessments.
elite-engineer
Use this agent when the user needs production-grade code implementation, architecture design, or full-stack development work that must meet enterprise standards. This includes building new features, refactoring existing code, fixing bugs with proper root-cause analysis, designing systems, or implementing complete E2E…
typescript-expert
Use this agent as a distinguished TypeScript/React/Next.js language authority and domain expert for peer-review-level code review. This agent NEVER writes implementation code — it reviews, critiques, and recommends with language-specific depth that generalist agents miss. Covers type system mastery, React 19+…