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/boettiger-lab/mcp-data-server/agents-mdgit clone --depth 1 https://github.com/boettiger-lab/mcp-data-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/boettiger-lab/mcp-data-server/agents-md)<a href="https://agentmods.dev/instructions/boettiger-lab/mcp-data-server/agents-md"><img src="https://agentmods.dev/badge/instructions/boettiger-lab/mcp-data-server/agents-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.07762 | $0.07762 |
| Opus 5 | $0.03881 | $0.03881 |
| Sonnet 5 | $0.01552 | $0.01552 |
| Haiku 4.5 | $0.00776 | $0.00776 |
Grade A, and why
mcp-data-server AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
anonymous pull token against the registry v2 API works anywhere `curl` does — substitute How it starts
The opening of the file, as written. The whole thing — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Architecture
The
.mdfiles in this repo are runtime prompt artifacts, not documentation.server.pyloads them at startup and injects their content into MCP tool descriptions and prompts. Editing them changes what the agent is instructed to do.README.mdis the only human-facing documentation.
Development & test environment — READ FIRST
Dev is the pre-prod canary: it tracks main and is never repointed by hand.
dev-duckdb-mcp.nrp-nautilus.io runs the current :main build (pinned by digest,
≥2 replicas) precisely so merged changes are exercised on real infrastructure —
including cross-pod skew — before prod. All MCP/guidance testing runs against
dev, never a local process. Dev has one job; it is not a place to host a
branch. Repointing dev to a branch stomps main and decays into the hand-pinning
loop that keeps breaking it (#341/#366).
To test a change before it merges, do not repoint dev. Options:
- Merge-then-validate (works today): merge to
main→ dev rolls onto that digest → run the headless matrix withMCP_URL=dev. This is the current gate. - Preview env (planned, #366): a
previewlabel builds:pr-<n>for an ephemeraldev-pr-<n>— the build trigger and CI deploy land with the NRP deploy token. - Guidance PR gate (planned, #245): the matrix Job runs the PR's
server.pyas a sidecar (git-checkout of the branch — no image build) so the exact PR guidance is validated pre-merge.
Never run server.py (the MCP server) locally in this JupyterLab environment.
It loads DuckDB plus the full STAC catalog in-process; running it here OOM'd the shared
pod and took down the instance (2026-07-07). There is no "local MCP" testing path —
if you catch yourself starting server.py, uvicorn, or a wrapper that imports the
server on this machine, stop. The workflow is: land the change on dev (dev tracks
:main — see Rollout below), then validate on dev with the headless matrix
(see Validating guidance 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.
- 4d ago First seen · 501 lines · 7,762 tokens per session scan A 2bcb95409e8d
mcp-data-server AGENTS.md is an instructions file published in the GitHub repository boettiger-lab/mcp-data-server (23 stars, last pushed 13d ago), licensed BSD-3-Clause. It adds 7,762 tokens to every session, about $0.0388 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.