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/mapbox/mcp-docs-server/claude-mdgit clone --depth 1 https://github.com/mapbox/mcp-docs-serverWhat 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.01089 | $0.01089 |
| Opus 5 | $0.00544 | $0.00544 |
| Sonnet 5 | $0.00218 | $0.00218 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
mcp-docs-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 2d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mapbox MCP Documentation Server
An MCP server providing AI assistants with access to Mapbox documentation and reference materials. No Mapbox access token required for most tools.
Tech Stack
- Runtime: Node.js 22+
- Language: TypeScript (strict mode)
- Build:
tshy(dual ESM/CJS output) - Testing: Vitest
- Package Manager: npm
Project Structure
src/
├── index.ts # MCP server entry point
├── config/toolConfig.ts # CLI argument parser (--enable-tools, --disable-tools)
├── constants/ # Static data (API endpoint definitions, etc.)
├── resources/ # MCP resource implementations
│ ├── BaseResource.ts # Abstract base class for resources
│ ├── resourceRegistry.ts # Resource registration
│ ├── utils/docParser.ts # Shared doc parsing utilities
│ └── */ # Individual resource implementations
├── tools/ # MCP tool implementations
│ ├── BaseTool.ts # Abstract base class for tools
│ ├── toolRegistry.ts # Tool registration
│ └── */ # Individual tool implementations
└── utils/
├── httpPipeline.ts # HTTP pipeline with User-Agent, caching, retry
├── types.ts # Shared types (HttpRequest, etc.)
└── versionUtils.ts # Version info
test/ # Mirrors src/ structure
Key Patterns
Tool Architecture
All tools extend BaseTool<InputSchema, OutputSchema>:
export class MyTool extends BaseTool<
typeof MyInputSchema,
typeof MyOutputSchema
> {
readonly name = 'my_tool';
readonly description = '...';
readonly annotations = { title: 'My Tool', readOnlyHint: true, ... };
constructor({ httpRequest }: { httpRequest: HttpRequest }) {
super({ inputSchema: MyInputSchema, outputSchema: MyOutputSchema });
this.httpRequest = httpRequest;
}
protected async execute(
input: z.infer<typeof MyInputSchema>
): Promise<CallToolResult> {
// no accessToken param — docs tools don't need one
}
}
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.
- 2d ago First seen · 129 lines · 1,089 tokens per session scan A dbeda213b29d
mcp-docs-server CLAUDE.md is an instructions file published in the GitHub repository mapbox/mcp-docs-server (1 stars, last pushed 7d ago), licensed MIT. It adds 1,089 tokens to every session, about $0.0054 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.