Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/ythalorossy/openfda/claude-mdgit clone --depth 1 https://github.com/ythalorossy/openfdaWrote 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/ythalorossy/openfda/claude-md)<a href="https://agentmods.dev/instructions/ythalorossy/openfda/claude-md"><img src="https://agentmods.dev/badge/instructions/ythalorossy/openfda/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 | $0.00810 | $0.00810 |
| Opus 5 | $0.00405 | $0.00405 |
| Sonnet 5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
openfda 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Model Context Protocol (MCP) server that provides tools for querying drug information from the OpenFDA API. The server communicates over stdio and requires an OPENFDA_API_KEY environment variable.
Commands
npm run build # Compile TypeScript to dist/
npm run build:cli # Build + add shebang for bin entry (required for CLI)
npm run dev # Start development server
npm run test # Run Vitest tests
npm run test:ci # Run tests in CI mode (no watch)
npm run typecheck # TypeScript type checking
npm run lint # Run ESLint
For single test file: npx vitest run tests/ApiHandler.test.ts
Key Files
vite.config.ts: Vite build configuration; externalizes SDK for StdioServerTransport compatibilitytests/: Vitest test suite (13 tests across ApiHandler, OpenFDABuilder, ToolManager)
Architecture
Entry Point: src/index.ts
The MCP server is initialized with McpServer from @modelcontextprotocol/sdk. All tool handlers are defined here and registered via ToolManager.
Tool Registration Pattern
Tools are registered in src/index.ts using ToolManager.registerTool() with:
name: MCP tool identifierdescription: Human-readable description for AI consumersschema: Zod schema for input validationhandler: Async function receiving parsed input, returns{ content: [{ type: 'text', text: string }] }
Tool Registration Gotcha
The MCP SDK has a bug with Zod schema validation. Always use schema.shape instead of passing schema directly to server.tool().
Key Modules
OpenFDABuilder(src/OpenFDABuilder.ts): Constructs OpenFDA API URLs using fluent builder pattern. Accepts context (label,event,ndc), search query, and limit.ApiHandler(src/ApiHandler.ts): HTTP client with retry logic (exponential backoff), timeout handling, and OpenFDA-specific error categorization.ToolManager(src/ToolManager.ts): Thin wrapper aroundMcpServer.tool()registration.types.ts: TypeScript interfaces for OpenFDA API responses and error types.- Tool implementations (
src/drug/): Individual tool handlers (get-drug-by-name.ts,get-drug-by-ndc.ts, etc.) exported viasrc/drug/index.ts src/food/: NDC search implementation
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.
- 4d ago First seen · 69 lines · 810 tokens per session scan A 3f5f84716447
openfda CLAUDE.md is an instructions file published in the GitHub repository ythalorossy/openfda (4 stars, last pushed 5mo ago), licensed MIT. It adds 810 tokens to every session, about $0.0040 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.