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.
git clone --depth 1 https://github.com/lesleslie/neo4j-mcpWrote 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.
[](https://agentmods.dev/commands/lesleslie/neo4j-mcp/neo4j-schema)<a href="https://agentmods.dev/commands/lesleslie/neo4j-mcp/neo4j-schema"><img src="https://agentmods.dev/badge/commands/lesleslie/neo4j-mcp/neo4j-schema/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.
<a href="https://agentmods.dev/commands/lesleslie/neo4j-mcp/neo4j-schema"><img src="https://agentmods.dev/badge/commands/lesleslie/neo4j-mcp/neo4j-schema.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.00277 |
| Opus 5 | $0.00009 | $0.00138 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
neo4j-schema 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 11d 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.
What it actually says
/neo4j-schema
Inspect the live Neo4j schema using the neo4j MCP server.
Usage
/neo4j-schema [--labels] [--relationships] [--indexes] [--constraints]
Arguments:
--labels: include node labels and their property keys.--relationships: include relationship types and their property keys.--indexes: include index definitions.--constraints: include constraint definitions.
By default the server returns the full schema snapshot. Use the flags to narrow the output when you only need a slice.
Workflow
- Call
mcp__neo4j__health_checkto confirm the server and database are reachable. - Call
mcp__neo4j__get_schemawith the requested flag(s). If no flags are supplied, the full schema is returned. - Report the structure as a compact summary: list of labels, relationship types, indexes, and constraints.
Example
/neo4j-schema --labels --indexes
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.
- 11d ago First seen · 33 lines · 17 tokens per session scan A 5fc849027206
neo4j-schema is a command published in the GitHub repository lesleslie/neo4j-mcp (1 stars, last pushed 12d ago), licensed BSD-3-Clause. It adds 17 tokens to every session and 277 once invoked, about $0.0001 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.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
ingest
Manually add knowledge to the Weaviate store.
json.batch_delete
Delete multiple JSON documents or paths in one itemwise batch.
json.batch_get
Read multiple JSON values by document and path.
json.index.drop
Drop a JSON secondary index by name.