Borrowing it
Nothing to install: this file belongs to cyanheads/met-museum-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/met-museum-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/cyanheads/met-museum-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/met-museum-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/cyanheads/met-museum-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/met-museum-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.
<a href="https://agentmods.dev/instructions/cyanheads/met-museum-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/met-museum-mcp-server/agents-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.04927 | $0.04927 |
| Opus 5 | $0.02464 | $0.02464 |
| Sonnet 5 | $0.00985 | $0.00985 |
| Haiku 4.5 | $0.00493 | $0.00493 |
Grade A, and why
met-museum-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 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
78% identical to obsidian-mcp-server AGENTS.md — 289 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Protocol
Server: met-museum-mcp-server
Version: 0.2.6
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.mdcontains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.
Core Rules
- Logic throws, framework catches. Tool/resource handlers are pure — throw on failure, no
try/catch. PlainErroris fine; the framework catches, classifies, and formats. Use error factories (notFound(),validationError(), etc.) when the error code matters. - Use
ctx.logfor request-scoped logging. Noconsolecalls. - Use
ctx.statefor tenant-scoped storage. Never access persistence directly. - Need input the caller didn't supply?
return ctx.requestInput(...)and readctx.inputswhen the handler is re-entered. Neverawaitfor user input mid-handler. - Secrets in env vars only — never hardcoded.
- Close the loop on issues. When implementing work tracked by a GitHub issue, comment on the issue with what landed and close it. Do both — a comment without a close leaves stale issues open; a close without a comment leaves no record of what shipped. The comment is for future readers — state the concrete changes, not the conversation that produced them.
Patterns
Tool
import { tool, z } from '@cyanheads/mcp-ts-core';
import { getMetService } from '@/services/met/met-service.js';
export const metSearchCollections = tool('met_search_collections', {
description: 'Search the Metropolitan Museum of Art collection by keyword and optional filters.',
annotations: { readOnlyHint: true, idempotentHint: true },
input: z.object({
q: z.string().min(1).describe('Keyword query.'),
limit: z.number().int().min(1).max(500).default(20).describe('Max object IDs to return.'),
}),
output: z.object({
total: z.number().int().describe('Total matching objects.'),
objectIDs: z.array(z.number().int().describe('A Met object ID.')).describe('Matching IDs.'),
returned: z.number().int().describe('Count of IDs in this response.'),
truncated: z.boolean().describe('True when total > returned.'),
}),
async handler(input, ctx) {
const result = await getMetService().search({ q: input.q, limit: input.limit }, ctx);
ctx.log.info('Met search', { q: input.q, total: result.total });
return result;
},
// format() populates content[] — the markdown twin of structuredContent.
// Different clients read different surfaces (Claude Code → structuredContent,
// Claude Desktop → content[]); both must carry the same data.
// Enforced at lint time: every field in `output` must appear in the rendered text.
format: (result) => [{
type: 'text',
text: `**Total:** ${result.total} | **Returned:** ${result.returned}${result.truncated ? ' (truncated)' : ''}\n\n${result.objectIDs.join(', ')}`,
}],
});
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 First seen · 326 lines · 4,927 tokens per session scan A de8fdd1b2d7d
met-museum-mcp-server AGENTS.md is an instructions file published in the GitHub repository cyanheads/met-museum-mcp-server (4 stars, last pushed 18d ago), licensed Apache-2.0. It adds 4,927 tokens to every session, about $0.0246 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 289 lines, and is treated as a copy.
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.
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 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).
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.