cyanheads-mcp-server: Instructions file for Claude Code

AGENTS.md

cyanheads-mcp-server AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from cyanheads/cyanheads-mcp-server. It costs 6,125 tokens per session, scanned A, a copy of obsidian-mcp-server AGENTS.md, Apache-2.0.

Project instructions for developing the cyanheads MCP server, a catalog for finding tools and servers in the cyanheads MCP ecosystem. It documents the server's conventions, framework version, and two catalog tools.

In plain words
What is it for?
Use it when changing this server, especially its semantic catalog search, tool or server descriptions, connection URLs, and client-specific installation snippets.
Why use it?
It gives contributors the project's required rules and explains how catalog search and entry details are expected to work.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: Claude Code plugin machinery, but also the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is cyanheads/cyanheads-mcp-server's own configuration. It tells Claude Code, Codex and OpenCode how to work on cyanheads-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cyanheads-mcp-server configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/cyanheads/cyanheads-mcp-server/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/cyanheads/cyanheads-mcp-server

Made for: Claude Code, Codex, OpenCode.

Wrote 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.

agentmods badge for cyanheads-mcp-server AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cyanheads/cyanheads-mcp-server/agents-md/github.svg)](https://agentmods.dev/instructions/cyanheads/cyanheads-mcp-server/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/cyanheads/cyanheads-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/cyanheads-mcp-server/agents-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.

agentmods 80×15 button for cyanheads-mcp-server AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/cyanheads/cyanheads-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/cyanheads-mcp-server/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6,125 This file is loaded in full into every session.
When invoked 6,125 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 78% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.06125 $0.06125
Opus 5 $0.03062 $0.03062
Sonnet 5 $0.01225 $0.01225
Haiku 4.5 $0.00613 $0.00613

Measured 8d ago against content hash 4d3862d5ed0c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

cyanheads-mcp-server AGENTS.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 8d 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.

Origin

This is a copy

78% identical to obsidian-mcp-server AGENTS.md — 304 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.

AGENTS.md · 403 lines

How it starts

The opening of the file, as written. The whole thing — 403 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.4.1 Framework: @cyanheads/mcp-ts-core ^0.12.3 Engines: Bun ≥1.3.0, Node ≥24.0.0 MCP SDK: @modelcontextprotocol/server 2.0.0 Zod: ^4.4.3

Read the framework docs first: node_modules/@cyanheads/mcp-ts-core/CLAUDE.md contains 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 from Snowflake/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 index misses. A remote entry always wins, so the fallback self-heals to dead code if the generator ever starts emitting one. The record is never part of the vector index, so semantic search does not surface it — only exact-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:

  1. Re-run the setup skill — ensures CLAUDE.md, skills, structure, and metadata are populated and up to date with the current codebase
  2. Run the design-mcp-server skill — if the tool/resource surface hasn't been mapped yet, work through domain design
  3. Add tools/resources/prompts — scaffold new definitions using the add-tool, add-app-tool, add-resource, add-prompt skills
  4. Add services — scaffold domain service integrations using the add-service skill
  5. Add tests — scaffold tests for existing definitions using the add-test skill
  6. Field-test definitions — exercise tools/resources/prompts with real inputs using the field-test skill, get a report of issues and pain points
  7. Run devcheck — lint, format, typecheck, and security audit
  8. Run the security-pass skill — audit handlers for MCP-specific security gaps: output injection, scope blast radius, input sinks, tenant isolation
  9. Run the polish-docs-meta skill — finalize README, CHANGELOG, metadata, and agent protocol for shipping
  10. Run the maintenance skill — investigate changelogs, adopt upstream changes, and sync skills after bun update --latest

Read the full file on GitHub · 403 lines

Changes

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.

  1. 8d ago First seen · 403 lines · 6,125 tokens per session scan A 4d3862d5ed0c

Subscribe to this mod's changes

cyanheads-mcp-server AGENTS.md is an instructions file published in the GitHub repository cyanheads/cyanheads-mcp-server (1 stars, last pushed 18d ago), licensed Apache-2.0. It adds 6,125 tokens to every session, about $0.0306 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to obsidian-mcp-server AGENTS.md, differing in 304 lines, and is treated as a copy.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

deepseek-ai/deepseek-harness · 3,737 tokens