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/adonai-labs/agent-runwayWrote 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/adonai-labs/agent-runway/electron)<a href="https://agentmods.dev/rules/adonai-labs/agent-runway/electron"><img src="https://agentmods.dev/badge/rules/adonai-labs/agent-runway/electron/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/rules/adonai-labs/agent-runway/electron"><img src="https://agentmods.dev/badge/rules/adonai-labs/agent-runway/electron.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.00000 | $0.01345 |
| Opus 5.5 | $0.00000 | $0.00538 |
| Sonnet 5.5 | $0.00000 | $0.00269 |
| Haiku 4.5 | $0.00000 | $0.00135 |
Grade A, and why
electron 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 1mo 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electron Development Guidelines
Directives for building secure, performant Electron applications. Security first; process separation; resource management.
Process Model
- Main process: Node.js environment, system APIs, window creation, IPC handlers
- Renderer process: Chromium-based UI; no direct Node.js access
- IPC: Secure typed communication between processes only
Register global handlers for uncaughtException, unhandledRejection, and render-process-gone; log and shut down gracefully.
Project Structure
project-root/
├── src/
│ ├── main/ # Main process
│ │ ├── index.ts # Entry point
│ │ ├── preload.ts # Preload script
│ │ ├── services/ # Business logic, external services
│ │ ├── handlers/ # IPC handlers
│ │ ├── windows/ # Window management
│ │ └── utils/
│ ├── renderer/ # Renderer (React)
│ │ ├── main.tsx, App.tsx
│ │ ├── components/ # ui/, features/, layout/
│ │ ├── pages/, hooks/, stores/, services/, utils/
│ └── shared/ # Shared between processes
│ ├── types/ # TypeScript definitions
│ ├── constants/
│ └── ipc/ # IPC channel types
├── assets/, dist/, tests/, config/
- Co-locate related files; single responsibility per module
- Dependencies point inward toward domain logic
- Use path aliases:
@main/*,@renderer/*,@shared/*
Security Fundamentals
Context Isolation and Preload
- Always set
nodeIntegration: falseandcontextIsolation: true - Always use a preload script; never expose
process,require, orfsto the renderer - Expose only the minimal API surface via
contextBridge.exposeInMainWorld
// Preload: validate before invoking
saveFile: (data: string) => {
if (typeof data !== 'string' || data.length > 10000) throw new Error('Invalid data');
return ipcRenderer.invoke('save-file', data);
}
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.
- 1mo ago First seen · 159 lines · 0 tokens per session scan A eeecd29163ab
electron is a cursor rule published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,345 tokens. 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-09-03.
Other cursor rules, from other repositories
optimize-dry-solid-principles-cursorrules-prompt-f
Cursor rules for optimization development with DRY and SOLID principles integration.
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
code-review-en
Code Review Guidelines (English).
agent-master
Meta-orchestrator that classifies tasks and routes to the right combination of installed skills across caveman (output compression), superpowers (dev workflow), anthropic-skills (business/domain expertise), and wired tactical libraries (wshobson, davila7, impeccable, anthropic-official). 26 routing categories…
ai-dev-os-review
Performs a comprehensive self-review before creating a PR. Combines guideline compliance checking (L3) with design-level review (L2) and philosophical alignment (L1). Unlike @ai-dev-os-check which only checks rules, this also evaluates architecture decisions and code design quality.