neo4j-mcp: Instructions file for Codex

AGENTS.md

neo4j-mcp AGENTS.md is an instructions file for Codex, OpenCode from lesleslie/neo4j-mcp. It costs 321 tokens per session, scanned A, original, BSD-3-Clause.

A set of repository instructions for a Neo4j MCP server, where Neo4j is a database that stores connected data such as people, places, or relationships.

In plain words
What is it for?
It helps developers install dependencies, run tests and checks, organize server code, write database queries safely, and test graph-related behavior.
Why use it?
It gives contributors one place to find the project structure, development commands, coding rules, and testing expectations.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is lesleslie/neo4j-mcp's own configuration. It tells Codex and OpenCode how to work on neo4j-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything neo4j-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to lesleslie/neo4j-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/lesleslie/neo4j-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/lesleslie/neo4j-mcp

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 neo4j-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/lesleslie/neo4j-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/lesleslie/neo4j-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/lesleslie/neo4j-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/lesleslie/neo4j-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for neo4j-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/lesleslie/neo4j-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/lesleslie/neo4j-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 321 This file is loaded in full into every session.
When invoked 321 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00321 $0.00321
Opus 5 $0.00161 $0.00161
Sonnet 5 $0.00064 $0.00064
Haiku 4.5 $0.00032 $0.00032

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

Security

Grade A, and why

neo4j-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 8d 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 · 35 lines

What it actually says

Repository Guidelines

Project Structure & Module Organization

  • neo4j_mcp/ contains the MCP server package, including driver integration, query helpers, schemas, and tool definitions.
  • settings/ stores configuration defaults, and tests/ should mirror the package structure for query, node, relationship, and path coverage.
  • Keep operator guidance in root docs rather than ad hoc scripts.

Build, Test, and Development Commands

  • uv sync --group dev installs development dependencies.
  • Use the documented local stdio or HTTP server commands for smoke tests.
  • uv run pytest runs the test suite.
  • uv run ruff check neo4j_mcp tests and uv run ruff format neo4j_mcp tests cover linting and formatting.

Coding Style & Naming Conventions

  • Use explicit type hints, parameterized queries, and small composable helpers around the Neo4j driver.
  • Keep modules snake_case, classes PascalCase, and tool responses structured and validated.

Testing Guidelines

  • Add tests for Cypher execution, schema inspection, and path-finding behavior.
  • Prefer mocked or containerized graph setups over depending on a shared live database.

Commit & Pull Request Guidelines

  • Use focused commits such as feat(paths): add shortest path tool options.
  • PRs should call out query behavior changes, commands run, and any compatibility implications.

Security & Configuration Tips

  • Never commit database credentials or internal connection URIs.
  • Validate user-supplied labels, property filters, and query parameters strictly.
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. 8d ago First seen · 35 lines · 321 tokens per session scan A 30ba5220e7be

Subscribe to this mod's changes

neo4j-mcp AGENTS.md is an instructions file published in the GitHub repository lesleslie/neo4j-mcp (1 stars, last pushed 10d ago), licensed BSD-3-Clause. It adds 321 tokens to every session, about $0.0016 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

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.

vercel/next.js · 7,296 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,153 tokens

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

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

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,469 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