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/kostya-pakhomov/graphmindWrote 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/rules/kostya-pakhomov/graphmind/graphmind-memory)<a href="https://agentmods.dev/rules/kostya-pakhomov/graphmind/graphmind-memory"><img src="https://agentmods.dev/badge/rules/kostya-pakhomov/graphmind/graphmind-memory/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/rules/kostya-pakhomov/graphmind/graphmind-memory"><img src="https://agentmods.dev/badge/rules/kostya-pakhomov/graphmind/graphmind-memory.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.00298 | $0.00298 |
| Opus 5.5 | $0.00119 | $0.00119 |
| Sonnet 5.5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
graphmind-memory 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 1mo 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
GraphMind — память между сессиями
Cursor/Kodik не помнит прошлые чаты. Память — только через MCP graphmind.
Справочник инструментов: docs/TOOLS.md
Старт (до основной работы)
bootstrap_memory({ cwd: "<PROJECT_ROOT>", query: "<суть задачи>", depth: 1 })
cwd — абсолютный путь хоста. Не пропускай.
В процессе — workspace
record_action({ summary })после значимых шагов (≤200 символов).- Hook
postToolUse: напоминание после 2+ правок (throttle ~45 с). - Факт этого репо:
propose_new_memory({ level: "L2", node_type: "atom", content }).
Кросс-проектная память (scope: "global")
propose_new_memory({ level: "L2", node_type: "atom", scope: "global", content: "# ..." })
scope: "global" |
workspace |
|---|---|
| Hooks, MCP, Docker, CI, конвенции | Код и факты только этого приложения |
Конец сессии
flush_session_memory({ summary: "итог сессии" })
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.
- 1mo ago First seen · 41 lines · 298 tokens per session scan A c44bb1727f2b
graphmind-memory is a cursor rule published in the GitHub repository kostya-pakhomov/graphmind (2 stars, last pushed 3mo ago), licensed MIT. It adds 298 tokens to every session, about $0.0012 per session on Opus 5.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 cursor rules, from other repositories
memforge-auto-recall
Rules that make an AI assistant automatically retrieve and save team memories during conversations.
memforge-topology-trigger
A set of rules for creating and querying a visual map of how services and repositories in a product relate to one another. The map is shown in Memforge WebUI, a browser interface for viewing this information.
memforge-codebase-memory-routing
Code-discovery rules for projects connected to Codegraph, a service that indexes code structure for queries. They define when to use Codegraph and when to use ordinary file searches.
04-spatial-parser
Guidelines for Spatial RAG and Markdown parsing.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.