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/elvatis/elvatis-mcp/claude-mdgit clone --depth 1 https://github.com/elvatis/elvatis-mcpWrote 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/elvatis/elvatis-mcp/claude-md)<a href="https://agentmods.dev/instructions/elvatis/elvatis-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/elvatis/elvatis-mcp/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.1 | $0.01963 | $0.01963 |
| Opus 5 | $0.00981 | $0.00981 |
| Sonnet 5 | $0.00393 | $0.00393 |
| Haiku 4.5 | $0.00196 | $0.00196 |
Grade A, and why
elvatis-mcp CLAUDE.md scanned grade A with 1 finding 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 5d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
ssh.ts <- SSH exec helper for remote commands (child_process.spawn, no extra deps) How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - elvatis-mcp
MCP server exposing OpenClaw tools (Home Assistant, memory, cron, sub-agent orchestration) to Claude Desktop, Cursor, Windsurf, and any MCP client.
Quick Commands
/build- typecheck + compile/status- show project status/ship- pre-publish checklist
Stack
- TypeScript 5.x strict, Node.js 18+, CommonJS output
@modelcontextprotocol/sdk1.x (stay on 1.x, v2 is pre-alpha)- Zod 3.x for all tool schemas
dotenv16.x for configuration
TS2589 Fix (resolved 2026-03-31)
MCP SDK server.tool() has 6 overloads that caused 47M+ type instantiations and OOM.
Solution: registerTool() wrapper in index.ts casts server to any before calling .tool(), bypassing overload resolution entirely. Schemas are z.object() in tool files, .shape is passed to the SDK. Build: 0.85s, 148 MB, 30k instantiations.
Rule: Never call server.tool() directly. Always use registerTool().
Key Rules
- No em dashes anywhere - use commas, colons, or parentheses
- Tool names:
domain_actionformat - Tool descriptions must be precise - Claude uses them for tool selection
- All secrets via env vars only - never hardcode tokens or IPs
- Logs to stderr only in stdio mode (stdout = MCP protocol stream)
- Build:
npm run build(avoid building on machines with limited RAM - tsc is memory-intensive)
Project Layout
src/
index.ts <- MCP server entry, tool registration (registerTool wrapper), transport setup
config.ts <- env var config (loads from .env, all values required or optional)
ssh.ts <- SSH exec helper for remote commands (child_process.spawn, no extra deps)
spawn.ts <- Local process spawner for gemini, codex, and claude CLI subprocesses
tools/
home.ts <- Home Assistant: light, climate, scene, vacuum, sensors, get_state
home-automation.ts <- home_automation: natural language HA commands via OpenClaw
memory.ts <- Daily memory log: write, read_today, search (SSH to server)
cron.ts <- OpenClaw cron: list, run, status (SSH to server)
cron-manage.ts <- OpenClaw cron management: create, edit, delete, history
openclaw.ts <- Sub-agent orchestration via SSH: run, status, plugins
openclaw-logs.ts <- openclaw_logs: tail OpenClaw server logs via SSH
notify.ts <- openclaw_notify: send notifications via WhatsApp/Telegram
gemini.ts <- Google Gemini sub-agent via local gemini CLI (headless mode)
codex.ts <- OpenAI Codex sub-agent via local codex CLI (full-auto + JSONL)
claude.ts <- Claude sub-agent via local claude CLI (JSON output, homedir cwd, Opus-only session resume)
local-llm.ts <- Local LLM sub-agent via OpenAI-compatible API (Ollama, LM Studio)
local-llm-models.ts <- local_llm_models: list available models from local LLM server
llama-server.ts <- llama_server: start/stop llama.cpp server for local inference
splitter.ts <- prompt_split: analyze complex prompts, split into sub-tasks with agent routing
routing-rules.ts <- Shared routing rules, keyword matching, agent constants (used by help + splitter)
split-execute.ts <- prompt_split_execute: execute a SplitPlan with agent dispatch and rate limiting
help.ts <- mcp_help routing guide and task-to-tool recommender
system-status.ts <- system_status: check host system health (CPU, RAM, disk, GPU)
file-transfer.ts <- file_transfer: upload/download files to/from OpenClaw server via SCP
rate-limiter.ts <- Rate limiting + cost tracking for cloud sub-agents (persistent JSON storage)
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.
- 5d ago First seen · 135 lines · 1,963 tokens per session scan A d6c00c52ffaa
elvatis-mcp CLAUDE.md is an instructions file published in the GitHub repository elvatis/elvatis-mcp (0 stars, last pushed 10d ago), licensed Apache-2.0. It adds 1,963 tokens to every session, about $0.0098 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
Kokoro-Engine CLAUDE.md
Claude Code instructions for chyinan/Kokoro-Engine, covering claude.md, git 规范, 项目概述, 常用命令 and 安装依赖.
retry-axios GEMINI.md
Gemini CLI instructions for JustinBeckwith/retry-axios, covering project: retry-axios, project overview, building and running, dependencies and commands.
openmcp-client CLAUDE.md
Instructions for LSTM-Kirigaya/openmcp-client, covering claude.md, development commands, setup and installation, development and service development.
bedrock CLAUDE.md
Claude Code instructions for christopher-buss/bedrock, covering bedrock project context, what is bedrock?, architecture, architecture quick reference and testing requirements (non-negotiable).
free-ai-gateway AGENTS.md
Instructions for zaber-dev/free-ai-gateway, covering 🤖 free-ai gateway - agentic development guidelines, 🏛️ monorepo architecture & package boundaries, 🛑 strict architectural rules for agents, 💻 essential developer commands and build all packages across monorepo.
loadout typescript.instructions.md
TypeScript Engineering Instructions (CLI + API + UI, framework-agnostic).