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 instructions/halilural/electron-mcp-server/claude-mdgit clone --depth 1 https://github.com/halilural/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/instructions/halilural/electron-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/halilural/electron-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/halilural/electron-mcp-server/claude-md.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.00330 | $0.00330 |
| Opus 5 | $0.00165 | $0.00165 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
electron-mcp-server CLAUDE.md 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 4d 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
Project guidelines
Git
- Do not add
Co-Authored-By: Claude ...or any other Claude/Anthropic attribution to commit messages. - Do not add a "Generated with Claude Code" footer to pull request bodies.
- Commit messages: conventional-commit subject (
feat:,fix:,ci:,docs:,chore:), plus a body only when the change needs explaining. - Work on a branch and open a PR against
master; don't push directly tomaster.
Development
- Node.js 20+ is required (the build toolchain and runtime dependencies dropped 18).
- Before pushing:
npm run code:check(lint + format check),npm run test:unit,npm run build. npm testincludestests/integration/electron-security-integration.test.ts, which needs a live Electron window with remote debugging on port 9222 and times out in headless environments. CI runstest:unitonly.
Releases
- Publishing is automated: creating a GitHub Release triggers
.github/workflows/publish.yml, which publishes to npm with provenance using theNPM_TOKENsecret. - Bump the version with
npm version <patch|minor|major>and push with--follow-tagsbefore creating the release. - README badges are proxied through GitHub's camo cache, keyed by URL. If a badge shows stale data, changing the URL (e.g. the
cacheSecondsquery param) is the only reliable way to refresh it.
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.
- 4d ago First seen · 21 lines · 330 tokens per session scan A dc614bece0be
electron-mcp-server CLAUDE.md is an instructions file published in the GitHub repository halilural/electron-mcp-server (71 stars, last pushed 28d ago), licensed MIT. It adds 330 tokens to every session, about $0.0016 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-30.
Other instructions, from other repositories
rn-agent-observer AGENTS.md
AGENTS.md instructions for GinzaTech/rn-agent-observer, covering rn agent observer instructions, lệnh chính, bản đồ workspace, ràng buộc code and fixture demo (đừng "sửa").
dev3000 AGENTS.md
Instructions for vercel-labs/dev3000, covering agents.md, runtime, local ui, production workflows, browser tools and development rules.
agent-inspect AGENTS.md
AGENTS.md instructions for rajudandigam/agent-inspect, covering agentinspect ai maintainer instructions, product boundary, source of truth, public-copy rule and start every task.
jenkins-cli CLAUDE.md
Instructions for avivsinai/jenkins-cli, covering claude.md, build & test commands, run a single test, skip e2e tests during unit testing and e2e with colima on macos (if docker is unreachable).
patchloom AGENTS.md
AGENTS.md instructions for patchloom/patchloom, covering agents.md, project overview, dev commands, git hygiene and release prs (release-please).
ducklab AGENTS.md
Instructions for jrullan/ducklab, covering working in this repository as an agent and path 1: conventional (edit the tree directly).