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/roklenarcic/mcp-server/claude-mdgit clone --depth 1 https://github.com/RokLenarcic/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/roklenarcic/mcp-server/claude-md)<a href="https://agentmods.dev/instructions/roklenarcic/mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/roklenarcic/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.00936 | $0.00936 |
| Opus 5 | $0.00468 | $0.00468 |
| Sonnet 5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
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 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.
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 — 93 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
This is a Clojure library for building MCP (Model Context Protocol) servers. It provides a flexible, lightweight framework that allows developers to choose their own JSON parsers, web servers, and async patterns rather than forcing specific technology choices.
Key Architecture
The library follows a layered architecture:
- Core protocols (src/main/org/clojars/roklenarcic/mcp_server/protocol.clj) - Define contracts for content types and responses
- Main API (src/main/org/clojars/roklenarcic/mcp_server/core.clj) - Primary public API with helper functions for creating MCP objects
- Server management (src/main/org/clojars/roklenarcic/mcp_server/server.clj) - Session management, handler registration, server lifecycle
- JSON-RPC layer (src/main/org/clojars/roklenarcic/mcp_server/json_rpc.clj) - JSON-RPC protocol implementation
- Transport layer (src/main/org/clojars/roklenarcic/mcp_server/server/) - HTTP, SSE, and stream-based transports
- Handlers (src/main/org/clojars/roklenarcic/mcp_server/handler/) - Built-in handlers for MCP operations
- JSON implementations (src/main/org/clojars/roklenarcic/mcp_server/json/) - Pluggable JSON serialization adapters
Session Architecture
Sessions are the central abstraction - they're maps stored in atoms that represent client connections. Sessions contain:
- Server info and capabilities
- JSON serialization implementation
- Dispatch table for RPC handlers
- Tools, prompts, resources, and completion handlers
- Connection-specific context data
Development Commands
Testing
# Run all tests
clj -M:test -m cognitect.test-runner
# Run tests for a specific namespace
clj -M:test -m cognitect.test-runner -n org.clojars.roklenarcic.mcp-server.core-test
# Run a specific test function
clj -M:test -m cognitect.test-runner -v org.clojars.roklenarcic.mcp-server.core-test/request-exchange-test
# Tests are located in test/ directory
# Uses test-check for property-based testing
# Uses matcher-combinators for test assertions
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 · 93 lines · 936 tokens per session scan A 82772567995e
mcp-server CLAUDE.md is an instructions file published in the GitHub repository RokLenarcic/mcp-server (16 stars, last pushed 1mo ago), licensed MIT. It adds 936 tokens to every session, about $0.0047 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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.