python-docs-mcp-server AGENTS.md

Repository instructions for a read-only MCP server that answers version-specific questions about Python's standard-library documentation. The Python standard library is the set of modules included with Python itself.

In plain words
What is it for?
Use it when changing the repository, following its autonomous-agent process, or testing its MCP documentation lookup flow.
Why use it?
It gives coding agents project rules, required checks, and review boundaries when working on this documentation server.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/ayhammouda/python-docs-mcp-server/agents-md
Clone the repo
git clone --depth 1 https://github.com/ayhammouda/python-docs-mcp-server

Made for: Codex, OpenCode.

Per session 902 This file is loaded in full into every session.
When invoked 902 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00902 $0.00902
Opus 5 $0.00451 $0.00451
Sonnet 5 $0.00180 $0.00180
Haiku 4.5 $0.00090 $0.00090

Measured 2d ago against content hash 96c98ce358cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

python-docs-mcp-server 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 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.

AGENTS.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidance

Project

python-docs-mcp-server is a read-only MCP server for the official Python standard library documentation. It is built for end users who want precise, version-aware stdlib answers inside MCP clients such as Claude, Cursor, and Codex without relying on an external hosted docs API at query time.

The repo's public credibility matters. Prefer changes that make the project easier to trust, easier to verify, and easier to contribute to over changes that merely add more AI or MCP setup.

Autonomous Agent Execution

A portion of this project is executed by autonomous coding agents working unattended against GitHub issues. If you are such an agent — or are scoping work for one — AGENT-EXECUTION-PIPELINE.md is mandatory reading before you touch anything. It defines the forbidden territory (don't-touch paths), the required issue structure, the canonical validation gate, the human-review triggers, and the recovery procedure. The what and why lives in STRATEGIC-ROADMAP-2026-05-29.md; the how, with what guardrails lives in the pipeline doc. Agents work on branches only, every PR needs human review, and auto-merge is forbidden. Per-issue working context lives under .planning/agent-context/<issue-slug>.md.

Canonical Commands

If uv is not installed yet:

python -m pip install uv

Bootstrap the repo:

uv sync --dev

If uv is not on your PATH after installation, reopen the shell or use python -m uv ... as a fallback.

Core verification commands:

uv run ruff check src/ tests/
uv run pyright src/
uv run pytest --tb=short -q

Build and inspect a local docs index:

uv run python-docs-mcp-server build-index --versions 3.12,3.13
uv run python-docs-mcp-server doctor
uv run python-docs-mcp-server validate-corpus

Package smoke check:

uv build

MCP Testing Flow

Use this order when validating MCP behavior:

  1. Run the automated checks above.
  2. Use MCP Inspector for quick local iteration.
  3. Confirm real-client behavior with the runbook in .github/INTEGRATION-TEST.md.

Read the full file on GitHub · 114 lines

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.

  1. 2d ago First seen · 114 lines · 902 tokens per session scan A 96c98ce358cb

Subscribe to this mod's changes

python-docs-mcp-server AGENTS.md is an instructions file published in the GitHub repository ayhammouda/python-docs-mcp-server (7 stars, last pushed 8d ago), licensed MIT. It adds 902 tokens to every session, about $0.0045 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.