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 rules/ohah/electron-mcp-server/architecture-rulesgit clone --depth 1 https://github.com/ohah/electron-mcp-serverWrote 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/ohah/electron-mcp-server/architecture-rules)<a href="https://agentmods.dev/rules/ohah/electron-mcp-server/architecture-rules"><img src="https://agentmods.dev/badge/rules/ohah/electron-mcp-server/architecture-rules.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.00020 | $0.00481 |
| Opus 5 | $0.00010 | $0.00241 |
| Sonnet 5 | $0.00004 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
architecture-rules 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.
What it actually says
아키텍처 규칙 (Tools 중심)
MCP 서버 패키지(packages/electron-mcp-server/src) 구조와 코드 분리 시 적용한다.
1. utils 사용 금지
- 툴 전용·공유 로직 모두
tools/아래에 둔다.utils/같은 별도 유틸 폴더를 만들지 않는다. - 여러 툴에서 쓰는 공통 로직이 있으면, tools 안에 하위 폴더를 만들고
index.ts로 노출한다.- 예:
tools/electron/index.ts— CDP/Electron 발견·실행 등 여러 툴이 공유하는 로직.
- 예:
2. tools 구조
- 한 툴 = 한 파일 (예:
tools/window-info.ts,tools/screenshot.ts,tools/command.ts). - 한 툴(또는 공유 모듈)의 코드가 커지면:
tools/<이름>/폴더를 만들고,index.ts에서 툴 등록·외부에 필요한 것만 export 하고,- 나머지 구현은 같은 폴더 안의 다른 파일로 쪼갠다.
- 예시:
tools/electron/index.ts— 스캔, 타겟, executeInElectron 등 export.tools/screenshot.ts— take_screenshot 툴; 필요 시 나중에tools/screenshot/index.ts+ 내부 파일로 분리.
3. 정리
| 상황 | 위치 |
|---|---|
| 단일 MCP 툴 (코드 적음) | tools/<툴이름>.ts |
| 단일 툴이 커짐 | tools/<툴이름>/index.ts + 같은 폴더 내 파일 분리 |
| 여러 툴이 쓰는 공통 로직 | tools/<공통이름>/index.ts (예: tools/electron/) |
utils 폴더는 만들지 않는다.
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 · 36 lines · 20 tokens per session scan A 3d352aac2ddc
architecture-rules is a cursor rule published in the GitHub repository ohah/electron-mcp-server (4 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 481 once invoked, about $0.0001 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.