Borrowing it
Nothing to install: this file belongs to cyanheads/cyanheads-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/cyanheads-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/cyanheads/cyanheads-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/cyanheads-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/cyanheads/cyanheads-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/cyanheads-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/cyanheads-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/cyanheads-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.08339 | $0.08339 |
| Opus 5.5 | $0.03336 | $0.03336 |
| Sonnet 5.5 | $0.01668 | $0.01668 |
| Haiku 4.5 | $0.00834 | $0.00834 |
Grade A, and why
cyanheads-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 yesterday.
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
78% identical to obsidian-mcp-server AGENTS.md — 357 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 — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Protocol
Server: cyanheads-mcp-server
Version: 0.5.0
Framework: @cyanheads/mcp-ts-core ^0.13.18
Engines: Bun ≥1.4.0, Node ≥24.0.0
MCP SDK: @modelcontextprotocol/server 2.4.0
Zod: ^4.6.7
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.
What This Server Is
A fleet discovery surface for the cyanheads MCP ecosystem. Two tools:
cyanheads_search_catalog— semantic search across fleet tools and servers using cosine similarity over Matryoshka-truncated 256-dim embeddings fromSnowflake/snowflake-arctic-embed-m-v1.5.cyanheads_describe_entry— returns the description, connection URL, and per-client install snippet for any named tool or server.
The catalog (fleet.json) is produced by caseyjhand-portfolio/scripts/build-fleet-json.ts at portfolio deploy time. Document vectors are baked into the JSON. The server only embeds the user's query at runtime via @huggingface/transformers. See docs/design.md for the full architecture.
The generated catalog does not include this server, so src/services/catalog/self-record.ts supplies a static CatalogRecord for cyanheads-mcp-server that CatalogService.getServer() / getTool() consult only after the remote namespace has no candidate — or, for getTool() scoped to server: "cyanheads-mcp-server", when that server's remote entry lacks the tool. Exact remote names win, then unique case-insensitive remote names; ambiguous folds never fall through to self. Output names are canonical. The self record is never part of the vector index, so semantic search does not surface it — only name resolution does.
What's Next?
When the user asks what's next or needs direction, suggest options based on the current project state. Common next steps:
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.
- yesterday Changed · +13 lines · +734 tokens per session 466f1ed1968d
- 3d ago Changed · -24 tokens per session a18da5159121
- 10d ago Changed · +41 tokens per session d0c9fefad8e3
- 29d ago Changed · +1 lines · +260 tokens per session a7b51b4bbaf5
- 1mo ago Changed · +29 lines · +1,203 tokens per session 49ec633ce2e0
- 1mo ago First seen · 403 lines · 6,125 tokens per session scan A 4d3862d5ed0c
cyanheads-mcp-server CLAUDE.md is an instructions file published in the GitHub repository cyanheads/cyanheads-mcp-server (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 8,339 tokens to every session, about $0.0334 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 78% identical to obsidian-mcp-server AGENTS.md, differing in 357 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).
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.