agentmods.dev

molmcp AGENTS.md

molmcp AGENTS.md is an instructions file for Codex, OpenCode from MolCrafts/molmcp. It costs 1,272 tokens per session, scanned A, original, BSD-3-Clause.

Project instructions for molmcp, a local service that connects AI assistants to MolCrafts and related providers. They explain the repository layout, development workflow, and rules for changing the code.

In plain words
What is it for?
Use them when developing molmcp, running its tests, updating documentation, or deciding how MCP tools and discovered Python science APIs should be organized.
Why use it?
They give the agent the project context needed to make consistent changes and avoid breaking important design decisions. They also clarify where source code, tests, documentation, notes, and settings belong.

Instructions file for CodexOpenCode

not rated 0 7d ago A scan 1,272 tokens original BSD-3-Clause
View the source file MolCrafts/molmcp
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/molcrafts/molmcp/agents-md
Clone the repo
git clone --depth 1 https://github.com/MolCrafts/molmcp

Made for: Codex, OpenCode.

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

agentmods badge for molmcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/molcrafts/molmcp/agents-md.svg)](https://agentmods.dev/instructions/molcrafts/molmcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/molcrafts/molmcp/agents-md"><img src="https://agentmods.dev/badge/instructions/molcrafts/molmcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,272 This file is loaded in full into every session.
When invoked 1,272 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.01272 $0.01272
Opus 5 $0.00636 $0.00636
Sonnet 5 $0.00254 $0.00254
Haiku 4.5 $0.00127 $0.00127

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

Security

Grade A, and why

molmcp 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 3d 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 · 119 lines

How it starts

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

AGENTS.md

What this repo is

molmcp is FastMCP-composed MCP for MolCrafts: molmcp serve starts the molcrafts core (knowledge plus list_planes / route) and mounts enabled providers with official namespaces (molvis_open). molmcp init <host> installs the usage skill and one MCP entry. Science APIs are discovered via the core and never mirrored as MCP tools. Pure Python (>= 3.12), src/ layout, managed with uv.

Protocol: MCP 2026-07-28 via FastMCP 4.0.0b5 + MCP Python SDK v2 (mcp>=2). Do not pin FastMCP back to 3.x without an explicit decision.

Where things live

  • Source code: src/molmcp/
  • Tests: tests/
  • Public documentation: docs/ (zensical site; concepts / guides / reference)
  • Passive project knowledge (notes, decisions, blueprint): .claude/notes/
  • Active runtime specs (alive, deleted on completion): .claude/specs/
  • Codex runtime config: .Codex/settings.local.json

One knowledge tree, two runtimes: notes and specs live under .claude/ and are read by both. Only runtime config is per-runtime.

Default workflow

For non-trivial work, prefer:

  1. plan (/mol:spec or write to .claude/notes/)
  2. implement (/mol:impl or /mol:fix)
  3. review (/mol:review)
  4. capture decisions (/mol:note)

What must never change casually

  • The molmcp.providers entry-point group — external packages register providers against it.
  • The discovery cache on-disk format (graph.db schema, manifests); bump SCHEMA_VERSION / ANALYZER_VERSION in src/molmcp/discovery/schema.py on any breaking change. Renaming a cache file means adding the old name to LEGACY_EXTRACT_DB_NAMES so nobody is left with a stranded multi-gigabyte orphan.
  • Agent-facing hint and error strings name tools bare, as registered; tests/test_tool_hints.py enforces it.
  • No environment variables — tests/test_no_env_switches.py fails the build if a module reads one, with three listed exemptions.
  • CI parity: .pre-commit-config.yaml mirrors .github/workflows/ci.yml step-for-step; change both in the same commit.

Read the full file on GitHub · 119 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. 3d ago First seen · 119 lines · 1,272 tokens per session scan A 79119e97dcde

Subscribe to this mod's changes

molmcp AGENTS.md is an instructions file published in the GitHub repository MolCrafts/molmcp (0 stars, last pushed 7d ago), licensed BSD-3-Clause. It adds 1,272 tokens to every session, about $0.0064 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

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

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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

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.

langchain-ai/langchain · 4,345 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

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