lifesciences-research: Command for Claude Code

.claude/commands/graphiti-verify.md

graphiti-verify is a command for Claude Code from donbr/lifesciences-research. It costs 11 tokens per session (1,073 once invoked), scanned A, original, MIT.

A command that runs a fixed first-day verification sequence for Graphiti environments. Graphiti is a system for storing and searching connected information.

In plain words
What is it for?
Use it to check server health, available data groups, and semantic search in the production and Docker-based development environments.
Why use it?
It checks whether the production and development databases respond correctly before further work begins.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the TodoWrite tool.

This is donbr/lifesciences-research's own configuration. It tells Claude Code how to work on lifesciences-research 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 lifesciences-research configures →

Reuse

Borrowing it

Nothing to install: this file belongs to donbr/lifesciences-research. 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/donbr/lifesciences-research/main/.claude/commands/graphiti-verify.md
Clone the repo
git clone --depth 1 https://github.com/donbr/lifesciences-research

Made for: Claude Code.

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 graphiti-verify

README.md
[![agentmods](https://agentmods.dev/badge/commands/donbr/lifesciences-research/graphiti-verify/github.svg)](https://agentmods.dev/commands/donbr/lifesciences-research/graphiti-verify)
Your own site
<a href="https://agentmods.dev/commands/donbr/lifesciences-research/graphiti-verify"><img src="https://agentmods.dev/badge/commands/donbr/lifesciences-research/graphiti-verify/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 graphiti-verify

Your own site · 80×15
<a href="https://agentmods.dev/commands/donbr/lifesciences-research/graphiti-verify"><img src="https://agentmods.dev/badge/commands/donbr/lifesciences-research/graphiti-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,073 The whole file, excluding the scripts and references it only reads on demand.
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.00011 $0.01073
Opus 5 $0.00005 $0.00536
Sonnet 5 $0.00002 $0.00215
Haiku 4.5 $0.00001 $0.00107

Measured 10d ago against content hash 1ef30451282b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

graphiti-verify 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 10d 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.

.claude/commands/graphiti-verify.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.

Run the Day 1 verification sequence to confirm the environment is working.

Instructions

Execute these checks in order. Report results but do NOT attempt fixes without user approval.

Environments checked:

  • Production: Neo4j Aura via graphiti-aura MCP (Checks 1-4)
  • Development: Docker Neo4j via graphiti-docker MCP (Check 5)

Check 1: Server Health

mcp__graphiti-aura__get_status()

Expected: Status OK with database connection confirmed.

Check 2: Query Available Groups

mcp__neo4j-aura-cypher__read_neo4j_cypher(
    query="MATCH (e:Episodic) RETURN DISTINCT e.group_id AS group_id, count(*) AS episodes ORDER BY episodes DESC"
)

Expected: List of group_ids with episode counts. Primary groups are graphiti_meta_knowledge and graphiti_reference_docs.

Note: This check requires the neo4j-aura-cypher MCP server running. If unavailable, start it with:

docker compose -f docker/docker-compose-neo4j-mcp.yml --env-file .env up -d

Check 3: Test Semantic Search

mcp__graphiti-aura__search_nodes(
    query="graphiti best practices",
    group_ids=["graphiti_meta_knowledge"],
    max_nodes=5
)

Expected: Returns relevant entity nodes.

Check 4: Neo4j Aura Health (Optional)

# First, get available instances
mcp__neo4j-aura-management__list_instances()

# Then check health of your instance (replace with your instance ID)
mcp__neo4j-aura-management__get_instance_details(instance_ids=["your-instance-id"])

Expected:

  • Instance status: "running"
  • Memory allocation appropriate for workload
  • Graph size metrics (nodes/relationships) reported
  • Connection URL accessible

Health Indicators:

  • ✅ Status "running" with graph nodes/relationships counts
  • ⚠️ Warn if memory is 1GB and graph has >5000 nodes (may need scaling)
  • ❌ Status not "running" or connection errors

Note: This check requires the neo4j-aura-management MCP server running. If unavailable, start it with:

docker compose -f docker/docker-compose-neo4j-mcp.yml --env-file .env up -d

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. 10d ago First seen · 119 lines · 11 tokens per session scan A 1ef30451282b

Subscribe to this mod's changes

graphiti-verify is a command published in the GitHub repository donbr/lifesciences-research (7 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 1,073 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.