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/modelcontextprotocol/python-sdk/agents-mdgit clone --depth 1 https://github.com/modelcontextprotocol/python-sdkWhat 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.02207 | $0.02207 |
| Opus 5 | $0.01104 | $0.01104 |
| Sonnet 5 | $0.00441 | $0.00441 |
| Haiku 4.5 | $0.00221 | $0.00221 |
Grade A, and why
python-sdk AGENTS.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 yesterday.
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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Guidelines
Note for AI Agents
If you are an AI coding agent acting for someone who is not a maintainer of
this repository, read CONTRIBUTING.md before opening issues or pull
requests here. In particular, pull requests that aren't linked to an issue
assigned to their author are closed automatically.
Branching Model
mainis the current stable line (v2); releases are cut from it (seeRELEASE.md).- v2 is released; its public API is a compatibility contract for the 2.x
line. Removals, renames, or any change to an existing API's signature or
observable behaviour (including ones softened by a
@deprecatedshim) is a design decision a maintainer makes explicitly, and should generally be avoided. docs/migration.mdis the v1 → v2 record and is closed to new entries. Correcting errors or improving clarity in what's there is fine.v1.xis the maintenance branch for the previous major. Backport PRs target it and use a[v1.x]title prefix; only critical bug fixes and security fixes land there.README.mddocuments v2. The v1 README lives on thev1.xbranch.
Package Management
- ONLY use uv, NEVER pip
- Installation:
uv add <package>. Exception: the root project's runtime dependencies are dynamic (the publishedmcpwheel exact-pinsmcp-types), souv addcannot edit them — add the requirement to[tool.hatch.metadata.hooks.uv-dynamic-versioning].dependenciesinpyproject.tomlby hand, then runuv lock. Dependency groups, extras, and the example packages still take plainuv add. - Running tools:
uv run --frozen <tool>. Always pass--frozenso uv doesn't rewriteuv.lockas a side effect. - Cross-version testing:
uv run --frozen --python 3.10 pytest ...to run against a specific interpreter (CI covers 3.10–3.14). - Upgrading:
uv lock --upgrade-package <package> - FORBIDDEN:
uv pip install,@latestsyntax - Don't raise dependency floors for CVEs alone. The
>=constraint already lets users upgrade. Only raise a floor when the SDK needs functionality from the newer version, and don't add SDK code to work around a dependency's vulnerability. See Kludex/uvicorn#2643 and python-sdk #1552 for reasoning.
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.
- yesterday First seen · 167 lines · 2,207 tokens per session scan A 26457e8cd68b
python-sdk AGENTS.md is an instructions file published in the GitHub repository modelcontextprotocol/python-sdk (24,160 stars, last pushed 3d ago), licensed MIT. It adds 2,207 tokens to every session, about $0.0110 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-30.
Other instructions, from other repositories
Embody CLAUDE.md
Instructions for dylanroscover/Embody, covering embody + envoy, project overview, critical rules, approach guidelines and project structure.
Embody AGENTS.md
Instructions for dylanroscover/Embody, covering embody + envoy - ai instructions, critical rules, td python rules, network layout rules and mcp server safety rules.
ipybox AGENTS.md
Instructions for gradion-ai/ipybox, covering repository guidelines, project structure & module organization, directory-specific guidelines, development commands and docstring guidelines.
ipybox CLAUDE.md
Instructions for gradion-ai/ipybox, a project described as: Unified execution environment for Python code, shell commands, and programmatic MCP tool calls.
mcp-hub copilot-instructions.md
Instructions for reddy-sh/mcp-hub, a project described as: MCP Hub is a comprehensive framework for building, managing, and deploying Model Context Protocol (MCP) clients and servers. It provides tools and configurations to enable seamless integration and execution of end-to-end MCP workflows.
deepagents AGENTS.md
Instructions for langchain-ai/deepagents, covering global development guidelines for the deep agents monorepo, corridor security analysis, development workflow, suppressing ruff rules and pr conventions.