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/topoteretes/cognee/agents-mdgit clone --depth 1 https://github.com/topoteretes/cogneeWrote 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/instructions/topoteretes/cognee/agents-md)<a href="https://agentmods.dev/instructions/topoteretes/cognee/agents-md"><img src="https://agentmods.dev/badge/instructions/topoteretes/cognee/agents-md.svg" alt="Measured on agentmods" 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 | $0.01909 | $0.01909 |
| Opus 5 | $0.00955 | $0.00955 |
| Sonnet 5 | $0.00382 | $0.00382 |
| Haiku 4.5 | $0.00191 | $0.00191 |
Grade A, and why
cognee 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
This document summarizes how to work with the cognee repository: how it’s organized, how to build, test, lint, and contribute. It mirrors our actual tooling and CI while providing quick commands for local development.
Project Structure & Module Organization
cognee/: Core Python library and API.api/: FastAPI application and versioned routers (add, cognify, memify, search, delete, users, datasets, responses, visualize, settings, sync, update, checks).cli/: CLI entry points and subcommands invoked viacognee/cognee-cli.infrastructure/: Databases, LLM providers, embeddings, loaders, and storage adapters.modules/: Domain logic (graph, retrieval, ontology, users, processing, observability, etc.).tasks/: Reusable tasks (e.g., code graph, web scraping, storage). Extend with new tasks here.eval_framework/: Evaluation utilities and adapters.shared/: Cross-cutting helpers (logging, settings, utils).tests/: Unit, integration, CLI, and end-to-end tests organized by feature.__main__.py: Entrypoint to route to CLI.
cognee-mcp/: Model Context Protocol server exposing cognee as MCP tools (SSE/HTTP/stdio). Contains its own README and Dockerfile.cognee-frontend/: Next.js UI for local development and demos.distributed/deploy/: One-click deployment templates (Modal, Fly.io, Railway, Render, Daytona).examples/: Example scripts demonstrating the public APIs and features (graph, code graph, multimodal, permissions, etc.).notebooks/: Jupyter notebooks for demos and tutorials.alembic/: Database migrations for relational backends.
Notes:
- Co-locate feature-specific helpers under their respective package (
modules/,infrastructure/, ortasks/). - Extend the system by adding new tasks, loaders, or retrievers rather than modifying core pipeline mechanisms.
Build, Test, and Development Commands
Python (root) – requires Python >= 3.10 and < 3.14. We recommend uv for speed and reproducibility.
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.
- 4d ago First seen · 165 lines · 1,909 tokens per session scan A f944240f7850
cognee AGENTS.md is an instructions file published in the GitHub repository topoteretes/cognee (30,435 stars, last pushed today), licensed Apache-2.0. It adds 1,909 tokens to every session, about $0.0095 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-30.
Other instructions, from other repositories
automem CLAUDE.md
Instructions for verygoodplugins/automem, covering claude.md, project overview, development commands, setup environment and development.
automem AGENTS.md
Instructions for verygoodplugins/automem, covering repository guidelines, project structure & modules, build, test, and development, coding style & naming and testing guidelines.
vellis AGENTS.md
Instructions for volantlabs/vellis, covering agents.md, repository purpose, startup checks, installing vellis for a user and model-first component workflow.
hindsight CLAUDE.md
Claude Code instructions for vectorize-io/hindsight, covering claude.md, project overview, development commands, local development (api + ui) and start both api server and control plane ui.
m_flow AGENTS.md
AGENTS.md instructions for FlowElement-xinliuyuansu/m_flow, covering m-flow — developer & agent reference, 1. repository map, extension points, 2. local development and python backend (requires python 3.10 – 3.13).
SwarmAI CLAUDE.md
Claude Code instructions for xg-gh-25/SwarmAI, covering claude.md, before you push — the local quality gate, commit identity, dev commands and conventions & invariants.