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/finite-sample/rmcp/claude-mdgit clone --depth 1 https://github.com/finite-sample/rmcpWhat 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.04683 | $0.04683 |
| Opus 5 | $0.02341 | $0.02341 |
| Sonnet 5 | $0.00937 | $0.00937 |
| Haiku 4.5 | $0.00468 | $0.00468 |
Grade A, and why
rmcp 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 2d 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 — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
RMCP (R Model Context Protocol) is a statistical analysis server that bridges AI assistants with R statistical computing capabilities through the Model Context Protocol.
Development Commands
Setup & Running (Hybrid Approach)
For Python-only development (cross-platform):
uv sync --group dev # Install minimal Python dependencies
uv run rmcp start # Start server in stdio mode (no R tools)
uv run rmcp serve-http # Start Streamable HTTP server
# Use configuration options
uv run rmcp --debug start # Enable debug mode
uv run rmcp --config config.json start # Use custom config file
RMCP_LOG_LEVEL=DEBUG uv run rmcp start # Use environment variables
# Shell completion (click provides it; zsh/bash/fish all verified)
eval "$(_RMCP_COMPLETE=zsh_source rmcp)" # bash needs 4.4+, macOS ships 3.2
Logs go to stderr as one JSON object per line — stdout carries the JSON-RPC
stream in stdio mode. Every record, whether from structlog or plain logging,
gets the same envelope, and anything logged while serving a request carries
request_id, so a tool call and its R execution can be tied together:
{"event": "tool completed", "tool": "linear_model", "duration_ms": 412,
"ok": true, "request_id": "7", "component": "registries.tools", ...}
For R integration development (Docker-based):
docker build --target development -t rmcp-dev . # Build R + Python dev environment
docker run -v $(pwd):/workspace -it rmcp-dev bash
# Inside container:
cd /workspace && pip install -e .
rmcp start # Full R integration available
For production deployment (optimized):
docker build --target production -t rmcp-production . # Multi-stage optimized build
docker run -p 8000:8000 rmcp-production rmcp serve-http # Production HTTP server
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.
- 2d ago First seen · 487 lines · 4,683 tokens per session scan A c17d88b34c90
rmcp CLAUDE.md is an instructions file published in the GitHub repository finite-sample/rmcp (211 stars, last pushed 6d ago), licensed MIT. It adds 4,683 tokens to every session, about $0.0234 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.