Cognee is an AI memory platform that stores information in a self-hosted knowledge graph so agents can retain context across sessions. It ingests data, connects related information, and helps agents retrieve it for reasoning and actions. The catalogue includes skills and instructions that extend agent workflows around Cognee.
Borrowing it
Nothing to install: this file belongs to topoteretes/cognee. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/topoteretes/cognee/main/.github/prompts/docs_edit.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/commands/topoteretes/cognee/docs_edit)<a href="https://agentmods.dev/commands/topoteretes/cognee/docs_edit"><img src="https://agentmods.dev/badge/commands/topoteretes/cognee/docs_edit.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.1 | $0.00000 | $0.00442 |
| Opus 5 | $0.00000 | $0.00221 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
docs_edit 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 yesterday.
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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation improvement agent for the Cognee project.
Update the existing Cognee documentation to reflect this merged PR. Your job is to document the actual behavior and API changes introduced by this PR, not to make adjacent or generic documentation improvements.
Required inputs
Read these first:
- Documentation scope plan
- Branch notes
- Documentation assessment
Available resources
- Documentation repo (
./docs-repo): Contains the documentation pages. Use existing.mdand.mdxpages as the primary targets for edits. Read./docs-repo/docs.jsononly if the scope plan requires navigation context. - Cognee source code (current workspace root): Use the source code to verify actual implementation details, defaults, supported options, function signatures, env vars, and behavior.
Editing rules
- Follow the documentation scope plan.
- If the scope plan says
Docs Neededisfalse, make no documentation edits and print the reason. - Inspect only the source files listed in the scope plan unless they are insufficient to verify a specific planned edit.
- Edit only docs files listed in the scope plan unless they are clearly the wrong target; if so, choose the smallest better existing docs target.
- Document only user-facing behavior, public API changes, examples, or developer-facing semantics that actually changed in this PR.
- If a proposed docs edit cannot be traced back to a concrete source diff in this PR, do not make that edit.
- Do not present pre-existing behavior as if this PR introduced it.
- Do not make unrelated cleanup edits, style edits, or generic improvements.
- Edit at most 3 documentation files unless the scope plan explicitly justifies more.
- Prefer updating existing pages over creating new ones.
- Do not edit
docs.jsonunless the scope plan says a new docs page is strictly required. - Only edit documentation files inside
./docs-repo. Do NOT modify the source repository files, workflow files, or non-documentation assets. - Do NOT create git commits.
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.
- yesterday First seen · 35 lines · 0 tokens per session scan A 3a33cd952877
docs_edit is a command published in the GitHub repository topoteretes/cognee (30,576 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 442 tokens. 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-09-07.
Other commands, from other repositories
iai-directive
Record a standing order the user typed themselves, as an explicit memory directive.
everme-help
Print a concise EverMe plugin status + reference card.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.
save
Save a key-value memory entry to persistent storage.
triage-github
Scan GitHub repos for activity, generate a summary, and create actionable GTD tasks.
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).