Borrowing it
Nothing to install: this file belongs to cyanheads/smithsonian-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/smithsonian-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/cyanheads/smithsonian-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/smithsonian-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/cyanheads/smithsonian-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/smithsonian-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.1 | $0.06090 | $0.06090 |
| Opus 5 | $0.03045 | $0.03045 |
| Sonnet 5 | $0.01218 | $0.01218 |
| Haiku 4.5 | $0.00609 | $0.00609 |
Grade A, and why
smithsonian-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 7d 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
84% identical to obsidian-mcp-server AGENTS.md — 306 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Protocol
Server: smithsonian-mcp-server
Version: 0.3.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.
What's Next?
When the user asks what's next or needs direction, suggest options based on the current project state. Common next steps:
- Re-run the
setupskill — ensures CLAUDE.md, skills, structure, and metadata are populated and up to date with the current codebase - Run the
design-mcp-serverskill — if the tool/resource surface hasn't been mapped yet, work through domain design - Add tools/resources/prompts — scaffold new definitions using the
add-tool,add-app-tool,add-resource,add-promptskills - Add services — scaffold domain service integrations using the
add-serviceskill - Add tests — scaffold tests for existing definitions using the
add-testskill - Field-test definitions — exercise tools/resources/prompts with real inputs using the
field-testskill, get a report of issues and pain points - Run
devcheck— lint, format, typecheck, and security audit - Run the
security-passskill — audit handlers for MCP-specific security gaps: output injection, scope blast radius, input sinks, tenant isolation - Run the
polish-docs-metaskill — finalize README, CHANGELOG, metadata, and agent protocol for shipping - Run the
maintenanceskill — investigate changelogs, adopt upstream changes, and sync skills afterbun update --latest
Tailor suggestions to what's actually missing or stale — don't recite the full list every time.
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. - 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.
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.
- 7d ago First seen · 403 lines · 6,090 tokens per session scan A 64d54a2cba79
smithsonian-mcp-server CLAUDE.md is an instructions file published in the GitHub repository cyanheads/smithsonian-mcp-server (2 stars, last pushed 13d ago), licensed Apache-2.0. It adds 6,090 tokens to every session, about $0.0304 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to obsidian-mcp-server AGENTS.md, differing in 306 lines, and is treated as a copy.
Other instructions, from other repositories
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).
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.
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 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).
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.