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/robertn702/mcp-openweathermap/claude-mdgit clone --depth 1 https://github.com/robertn702/mcp-openweathermapWrote 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/robertn702/mcp-openweathermap/claude-md)<a href="https://agentmods.dev/instructions/robertn702/mcp-openweathermap/claude-md"><img src="https://agentmods.dev/badge/instructions/robertn702/mcp-openweathermap/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.1 | $0.00629 | $0.00629 |
| Opus 5 | $0.00315 | $0.00315 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
mcp-openweathermap 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 5d 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.
Development Commands
# Development and testing
bun run dev # Run development server with .env file
bun run test # Run test suite
bun run test:watch # Run tests in watch mode
bun run typecheck # TypeScript type checking
bun run typecheck:watch # Type checking in watch mode
# Build and release
bun run build # Compile TypeScript to JavaScript
bun run release # Build and publish (with changesets)
# MCP Inspector for testing
bun run inspect # Test with MCP Inspector (dev)
bun run inspect:built # Test with MCP Inspector (built)
bun run inspect:http # Test with MCP Inspector (HTTP mode)
Architecture Overview
This is an MCP (Model Context Protocol) server that provides weather data integration through OpenWeatherMap API. It implements 11 weather-related tools using the FastMCP framework.
Core Components
- Main Entry Point (
src/main.ts): Implements all 11 weather tools with FastMCP framework - Authentication System (
src/auth/): Handles both HTTP bearer token and stdio environment variable authentication - Schema Validation (
src/schemas.ts): Zod schemas for all 11 tools with comprehensive input validation - Transport Configuration (
src/config/transport.ts): Environment-driven transport selection (stdio/HTTP stream)
Key Utilities
- Client Resolver (
src/utils/client-resolver.ts): Manages OpenWeatherAPI client instances with session-based caching - Location Parser (
src/utils/location-parser.ts): Parses coordinates, city names, and various location formats - Weather Formatter (
src/utils/weather-formatter.ts): Formats API responses for display
Transport Modes
The server supports dual transport modes:
- Stdio Transport (default): Uses
OPENWEATHER_API_KEYenvironment variable - HTTP Stream Transport: Uses Bearer token authentication
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.
- 5d ago First seen · 69 lines · 629 tokens per session scan A 7e4ee6deefe6
mcp-openweathermap CLAUDE.md is an instructions file published in the GitHub repository robertn702/mcp-openweathermap (5 stars, last pushed 1y ago), licensed MIT. It adds 629 tokens to every session, about $0.0031 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
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 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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).