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/skyflowfoundry/mcp_sample_tavily/claude-mdgit clone --depth 1 https://github.com/SkyflowFoundry/mcp_sample_tavilyWrote 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/skyflowfoundry/mcp_sample_tavily/claude-md)<a href="https://agentmods.dev/instructions/skyflowfoundry/mcp_sample_tavily/claude-md"><img src="https://agentmods.dev/badge/instructions/skyflowfoundry/mcp_sample_tavily/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.01256 | $0.01256 |
| Opus 5 | $0.00628 | $0.00628 |
| Sonnet 5 | $0.00251 | $0.00251 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
mcp_sample_tavily 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 3d 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 — 103 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 TypeScript-based Model Context Protocol (MCP) server for Tavily's advanced web search and data extraction capabilities with optional Skyflow deidentification integration. It enables AI assistants like Claude to interact with Tavily's search, extract, crawl, and map APIs through the MCP protocol while automatically protecting sensitive data through Skyflow's deidentification service.
Development Commands
Build and Development
npm run build- Compile TypeScript to JavaScript and set executable permissionsnpm run watch- Run TypeScript compiler in watch mode for developmentnpm run prepare- Runs build (used by npm install)npm run prepublishOnly- Runs build before publishing
Testing and Inspection
npm run inspector- Launch MCP inspector for debugging server toolsnpx tavily-mcp --list-tools- List available tools (requires TAVILY_API_KEY)npm test- Run all tests (Skyflow deidentification + integration tests)npm run test:skyflow- Run Skyflow deidentification tests onlynpm run test:integration- Run integration tests only
Running the Server
npx tavily-mcp- Run the server (requires TAVILY_API_KEY environment variable)node build/index.js- Run compiled server directly
With Skyflow Integration:
# Set required environment variables
export TAVILY_API_KEY=your_tavily_key
export SKYFLOW_VAULT_ID=your_vault_id
export SKYFLOW_CLUSTER_ID=your_cluster_id
export SKYFLOW_API_KEY=your_skyflow_key
# Run server with deidentification enabled
npx tavily-mcp
Architecture
Core Components
- TavilyClient class (
src/index.ts) - Main MCP server implementation with Skyflow integration - SkyflowClient class (
src/skyflow/client.ts) - Deidentification service wrapper - Four API endpoints: search, extract, crawl, map via Tavily's REST API
- Tool definitions with comprehensive input schemas for each API including deidentification options
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.
- 3d ago First seen · 103 lines · 1,256 tokens per session scan A 5b837a91ee48
mcp_sample_tavily CLAUDE.md is an instructions file published in the GitHub repository SkyflowFoundry/mcp_sample_tavily (0 stars, last pushed 11mo ago), licensed MIT. It adds 1,256 tokens to every session, about $0.0063 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.