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/heatherflux/serverless-mcp/claude-mdgit clone --depth 1 https://github.com/HeatherFlux/serverless-mcpWrote 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/heatherflux/serverless-mcp/claude-md)<a href="https://agentmods.dev/instructions/heatherflux/serverless-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/heatherflux/serverless-mcp/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.00723 | $0.00723 |
| Opus 5 | $0.00362 | $0.00362 |
| Sonnet 5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
serverless-mcp 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 — 77 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.
Common Commands
Development
pnpm dev- Watch mode for development with tsxpnpm test:watch- Run tests in watch mode with vitest
Testing
pnpm test- Run full test suite (vitest + typecheck + lint)pnpm test:coverage- Run tests with coverage reportvitest run src/tools/provider.test.ts- Run specific test filevitest run -t "test name"- Run specific test by name
Building
pnpm build:all- Build complete package (types + ESM)pnpm build:types- Generate TypeScript declarations onlypnpm build:esm- Build ESM modules onlypnpm clean- Remove dist directory
Code Quality
pnpm lint- Run Biome linterpnpm lint:fix- Auto-fix linting issuespnpm format- Format code with Biomepnpm typecheck- Run TypeScript type checking
Architecture Overview
This is a TypeScript implementation of the Model Context Protocol (MCP) with modular architecture optimized for serverless deployments, particularly AWS Lambda with streaming support.
Core Structure
The codebase follows a slice-based architecture where each MCP capability is isolated in its own module:
- core/ - JSON-RPC protocol implementation and main McpServer orchestrator
- prompts/ - Prompt template management with decorators and validation
- resources/ - Resource providers with caching support
- tools/ - Tool execution with middleware pipeline (timing, logging, rate limiting)
- roots/ - File system boundary management
- transports/ - Multiple transport layers (stdio, HTTP streaming, Lambda)
- lambda/ - AWS Lambda-specific handler with streaming response support
Key Design Patterns
Provider Pattern: Each slice (tools, resources, prompts, roots) implements a provider interface that the McpServer consumes. Providers handle registration, validation, and execution of their respective capabilities.
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 · 77 lines · 723 tokens per session scan A 52f507703327
serverless-mcp CLAUDE.md is an instructions file published in the GitHub repository HeatherFlux/serverless-mcp (2 stars, last pushed 11mo ago), licensed MIT. It adds 723 tokens to every session, about $0.0036 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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.