Borrowing it
Nothing to install: this file belongs to cyanheads/evals-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cyanheads/evals-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/cyanheads/evals-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/cyanheads/evals-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/cyanheads/evals-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/evals-mcp-server/claude-md/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/instructions/cyanheads/evals-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/evals-mcp-server/claude-md.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.07802 | $0.07802 |
| Opus 5.5 | $0.03121 | $0.03121 |
| Sonnet 5.5 | $0.01560 | $0.01560 |
| Haiku 4.5 | $0.00780 | $0.00780 |
Grade A, and why
evals-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 9d 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.
This is a copy
80% identical to obsidian-mcp-server AGENTS.md — 376 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Protocol
Server: evals-mcp-server
Version: 0.1.6
Framework: @cyanheads/mcp-ts-core ^0.13.15
Engines: Bun ≥1.4.0, Node ≥24.0.0
MCP SDK: @modelcontextprotocol/server ^2.3.1
Zod: ^4.6.5
Read the framework docs first:
node_modules/@cyanheads/mcp-ts-core/CLAUDE.mdcontains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.
This Server
evals-mcp-server turns an agent into an eval author. It's an authoring-loop server (not a data-source wrapper): the agent produces a verifiable eval record through a draft → review → surgical-revise → submit loop, and the server acts as both scribe (normalize, persist, compile) and adversarial checker (run the record's own grader, reject what doesn't hold up). No external API — the server is the source of truth, backed by plain JSON files under EVALS_DATA_DIR. Full concept + as-built surface: docs/design.md, docs/idea.md, docs/authoring-loop-pattern.md.
Surface (9 tools, 1 resource):
| Primitive | Purpose |
|---|---|
evals_describe_schema |
Required/optional fields + grader options for a task_type (static). |
evals_create_draft |
Create a draft; reflect it back with a review protocol + subagent prompt. |
evals_get_record |
Read a draft or submitted record by id. |
evals_revise_draft |
Surgical set/append/unset patch to a draft by dotted path. |
evals_discard_draft |
Delete a draft. |
evals_run_check |
Run a grader against candidates, PASS/REJECT, decoupled from any record. |
evals_submit_draft |
Committability gate → freeze. |
evals_list_records |
Filter records by status/domain/task_type/tag (summary projection). |
evals_export_records |
Compile submitted records to JSONL/CSV/Inspect/lm-eval under exports/. |
eval://record/{id} |
Resource mirror of evals_get_record. |
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.
- 9d ago Changed 1385a187431a
- 15d ago Changed · +1 lines · +181 tokens per session b58137272599
- 1mo ago Changed · +17 lines · +1,464 tokens per session a9ecaa4a2771
- 1mo ago First seen · 419 lines · 6,157 tokens per session scan A b6b97739e669
evals-mcp-server CLAUDE.md is an instructions file published in the GitHub repository cyanheads/evals-mcp-server (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 7,802 tokens to every session, about $0.0312 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to obsidian-mcp-server AGENTS.md, differing in 376 lines, and is treated as a copy.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.