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.
npx agentmods add instructions/getzep/graphiti/agents-mdgit clone --depth 1 https://github.com/getzep/graphitiWhat 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 | $0.01656 | $0.01656 |
| Opus 5 | $0.00828 | $0.00828 |
| Sonnet 5 | $0.00331 | $0.00331 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade B, and why
graphiti AGENTS.md scanned grade B with 1 finding 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Docker has no systemd here — start the daemon manually once per VM: `sudo dockerd > /tmp/dockerd.log 2>&1 &`. Then start the DBs on the host network exactly as CI does (see `.github/workflows/unit_tests.yml`): How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Graphiti's core library lives under graphiti_core/, split into domain modules such as nodes.py, edges.py, models/, and search/ for retrieval pipelines. Database drivers in graphiti_core/driver/ support Neo4j, FalkorDB, and Neptune (plus a deprecated Kuzu driver). Additional core modules include cross_encoder/ (reranking via BGE, OpenAI, and Gemini), telemetry/ (OpenTelemetry tracing), namespaces/ (namespace management), and migrations/ (database migrations). Service adapters and API glue reside in server/graph_service/, while the MCP integration lives in mcp_server/ (with its own src/, tests/, config/, and docker/ subdirectories). Shared assets sit in images/ and examples/. Tests cover the core package via tests/, with configuration in conftest.py, pytest.ini, and Docker compose files for optional services. Specifications live in spec/ and type signatures in signatures/. Tooling manifests live at the repo root, including pyproject.toml, Makefile, and deployment compose files.
Build, Test, and Development Commands
make install: install the dev environment (uv sync --extra dev).make format: runruffto sort imports and apply the canonical formatter.make lint: executeruffpluspyrighttype checks againstgraphiti_core.make test: run unit tests only, excluding integration tests and disabling non-Neo4j drivers (DISABLE_FALKORDB=1 DISABLE_KUZU=1 DISABLE_NEPTUNE=1 uv run pytest -m "not integration").make check: run format, lint, and test in sequence.uv run pytest tests/path/test_file.py: target a specific module or test selection.docker-compose -f docker-compose.test.yml up: provision local graph/search dependencies for integration flows.
Coding Style & Naming Conventions
Python code uses 4-space indentation, 100-character lines, and prefers single quotes as configured in pyproject.toml. Modules, files, and functions stay snake_case; Pydantic models in graphiti_core/models use PascalCase with explicit type hints. Keep side-effectful code inside drivers or adapters (graphiti_core/driver, graphiti_core/cross_encoder, graphiti_core/utils) and rely on pure helpers elsewhere. Run make format before committing to normalize imports and docstring formatting.
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.
- 2d ago First seen · 46 lines · 1,656 tokens per session scan B 068e33c30b0c
graphiti AGENTS.md is an instructions file published in the GitHub repository getzep/graphiti (30,424 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,656 tokens to every session, about $0.0083 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
crewAI AGENTS.md
AGENTS.md instructions for crewAIInc/crewAI, covering agent instructions for crewai oss, key guidelines, message content and changing docs.
fastmcp CLAUDE.md
Claude Code instructions for PrefectHQ/fastmcp, covering fastmcp development guidelines, required development workflow, repository structure, core mcp objects and development rules.
stagehand AGENTS.md
Instructions for browserbase/stagehand: Only a human may request changes to this file. Keep additions rare and limited to durable, repository-wide rules. -->.
autocontext CLAUDE.md
Instructions for greyhaven-ai/autocontext, covering claude.md, project overview, repository layout, commands and setup.
CodeBoarding AGENTS.md
AGENTS.md instructions for CodeBoarding/CodeBoarding, covering system-wide recommendations for agent execution, 1. environment and virtual environment setup, 2. dependency and repository navigation, 3. code quality and testing standards and 4. execution flow and tool patterns.
autocontext AGENTS.md
Instructions for greyhaven-ai/autocontext, covering agent guide, pick the right surface, working directories, setup and parity-last changes.