devdocs-mcp AGENTS.md

A project instruction file named AGENTS.md for developing devdocs-mcp, a tool that downloads programming documentation and supports search over it.

In plain words
What is it for?
Use it when working on devdocs-mcp, especially when adding MCP tools, changing document downloads or indexing, or running the project and its tests.
Why use it?
It gives coding agents the repository layout, setup commands, dependency options, and conventions they need before changing the project.

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/hellbutcher/devdocs-mcp/agents-md
Clone the repo
git clone --depth 1 https://github.com/HellButcher/devdocs-mcp

Made for: Codex, OpenCode.

Per session 663 This file is loaded in full into every session.
When invoked 663 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.00663 $0.00663
Opus 5 $0.00331 $0.00331
Sonnet 5 $0.00133 $0.00133
Haiku 4.5 $0.00066 $0.00066

Measured yesterday against content hash 2479027907c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devdocs-mcp 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.

AGENTS.md · 63 lines

How it starts

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

devdocs-mcp Development Guidelines

Project Structure

src/devdocs_mcp/
├── __init__.py      # Entry point
├── __main__.py      # CLI entry point with error handling
├── config.py        # XDG paths (platformdirs), settings, sources
├── catalog.py       # Fetches 819 docs from devdocs.io API
├── download.py      # Downloads/extracts .tar.gz bundles
├── embedder.py      # HTML→text extraction + SQLite metadata storage
├── chunking.py      # Document chunking strategies (sentence/paragraph)
├── http_utils.py    # Shared HTTP retry logic with exponential backoff
├── faiss_index.py   # FAISS vector index with IndexIDMap
└── mcp_server.py    # 10 MCP tools via FastMCP

Setup & Dependencies

  • Python >=3.13
  • uv sync for core deps (mcp, httpx, platformdirs)
  • uv sync --extra ml for ML deps (faiss-cpu, sentence-transformers, numpy)
  • ML deps are optional — server runs without them but semantic search requires them

Building New Tools

  1. Add tool function with @mcp.tool() decorator in mcp_server.py
  2. Import dependencies at top of file
  3. Keep tool descriptions clear and parameter types explicit
  4. Return strings for simple responses; use structured formatting for multi-field output

Code Style

  • Type hints on all public functions
  • Docstrings with Args/Returns sections
  • No print() in library code — use logging.getLogger(name)
  • Import order: stdlib → third-party → local (with noqa: E402 if needed)

Testing

uv run python -c "from devdocs_mcp.mcp_server import ML_AVAILABLE, list_docs; ..."

Adding New Doc Scrapers

devdocs.io bundles are served from https://downloads.devdocs.io/{slug}.tar.gz containing:

  • index.json — entry index with path/type info
  • db.json — page content map (path → HTML)
  • meta.json — metadata

New slugs can be added by downloading the tarball and extracting. The embedder handles all formats automatically.

Configuration

Config stored at XDG paths:

  • Config: ~/.config/devdocs-mcp/config.json
  • Cache: ~/.cache/devdocs-mcp/ (docs + embeddings)

Read the full file on GitHub · 63 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. yesterday First seen · 63 lines · 663 tokens per session scan A 2479027907c3

Subscribe to this mod's changes

devdocs-mcp AGENTS.md is an instructions file published in the GitHub repository HellButcher/devdocs-mcp (0 stars, last pushed 27d ago), licensed MIT. It adds 663 tokens to every session, about $0.0033 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.

Related

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.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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.

langchain-ai/langchain · 4,345 tokens