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/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/commit-rules)<a href="https://agentmods.dev/rules/ohah/electron-mcp-server/commit-rules"><img src="https://agentmods.dev/badge/rules/ohah/electron-mcp-server/commit-rules/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/ohah/electron-mcp-server/commit-rules"><img src="https://agentmods.dev/badge/rules/ohah/electron-mcp-server/commit-rules.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.00597 | $0.00597 |
| Opus 5.5 | $0.00239 | $0.00239 |
| Sonnet 5.5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
commit-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 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.
What it actually says
커밋 규칙
git 커밋을 만들거나 제안할 때 적용한다. 자세한 내용은 AGENTS.md 참고.
메시지 형식
<type>(<scope>): <subject>
<body>
<footer>
- Type (필수):
feat|fix|refactor|test|docs|chore|style - Scope (선택):
server|mcp|client|docs|scripts|config - Subject (필수): 명령형, 50자 이내, 마침표 없음. 한글로 작성.
- Body (선택): 72자마다 줄바꿈; 무엇을·왜 했는지 설명. 한글로 작성.
- Footer (선택): breaking change, 이슈 참조
원칙
- 커밋 하나당 목적 하나
- 관련 없는 변경은 별도 커밋으로 분리
- 각 커밋은 독립적으로 의미 있어야 함
- 작고 논리적인 단위 선호
예시
feat(mcp): MCP 서버용 stdio 트랜스포트 추가
- @modelcontextprotocol/sdk로 StdioServerTransport 구현
- Cursor/Claude Desktop용 샘플 도구 등록
fix(server): stdio 종료 시 연결 해제 처리
- 프로세스 종료 시 트랜스포트 정리
커밋 전 (필수)
도구 버전은 mise 사용 (.mise.toml 참고). 포맷/린트는 프로젝트의 bun을 쓰도록 mise exec -- 로 실행한다.
TypeScript/JavaScript: mise exec -- bun run format 실행 후 mise exec -- bun run lint 실행; 변경된 파일 스테이징 후 커밋.
커밋 후 (필수)
커밋한 뒤 MD 파일에 요약을 쓴다. 파일에는 다음이 포함되어야 한다.
- 제목 (예: 브랜치 이름 또는 커밋 제목)
- 작업 내용: 무엇을 했는지 — 목표, 변경 사항, 결과를 문장으로 (PR 스타일). 테스트 추가·수정이 있으면 언급 (예: "…에 대한 테스트 추가" 또는 "테스트 커버리지에 … 포함").
이 MD 파일은 커밋하지 않는다 (.gitignore에 넣거나 unstaged로 둔다).
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 · 62 lines · 597 tokens per session scan A 84cea1f610c6
commit-rules is a cursor rule published in the GitHub repository ohah/electron-mcp-server (4 stars, last pushed 7mo ago), licensed MIT. It adds 597 tokens to every session, about $0.0024 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-08-31.
Other cursor rules, from other repositories
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.