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 rules/nhadaututtheky/neural-memory/cursorrulesgit clone --depth 1 https://github.com/nhadaututtheky/neural-memoryWhat 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.00917 | $0.00917 |
| Opus 5 | $0.00458 | $0.00458 |
| Sonnet 5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
cursorrules 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 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.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory System — NeuralMemory
This workspace uses NeuralMemory for persistent memory across sessions. You have access to nmem_* MCP tools. Use them PROACTIVELY.
Session Start (ALWAYS)
nmem_recap()— Resume context from last sessionnmem_context(limit=20)— Load recent memoriesnmem_session(action="get")— Check current task/feature/progress
If gap_detected is true, run nmem_auto(action="flush", text="<recent context>") to recover.
During Work — Auto-Remember
When a DECISION is made: nmem_remember(content="Decision: ...", type="decision", priority=7, tags=["project-name"])
When a BUG is fixed: nmem_remember(content="Fixed: ... by ...", type="error", priority=7)
When user states a PREFERENCE: nmem_remember(content="User prefers ...", type="preference", priority=6)
When a FACT is learned: nmem_remember(content="...", type="fact", priority=5)
When a TODO is identified: nmem_todo(task="...", priority=6)
During Work — Recall Before Asking
ALWAYS check memory before asking the user a question: nmem_recall(query="", depth=1)
Depth: 0=instant, 1=context (default), 2=patterns, 3=deep traversal.
Session End
nmem_auto(action="process", text="") nmem_session(action="set", feature="...", task="...", progress=0.8)
Emergency Flush (before context reset)
nmem_auto(action="flush", text="")
Codebase Indexing (first time)
nmem_index(action="scan", path="./src")
After indexing, nmem_recall finds related code through the neural graph.
Project Context
nmem_eternal(action="save", project_name="MyApp", tech_stack=["React", "Node.js"]) nmem_eternal(action="save", decision="Use Redis", reason="Low latency caching")
Ephemeral Memories
For scratch notes, debugging context, or temporary reasoning: nmem_remember(content="...", ephemeral=true)
Auto-expires after 24h, never synced, excluded from consolidation. Filter them out: nmem_recall(query="...", permanent_only=true)
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 · 100 lines · 917 tokens per session scan A c395624f03aa
cursorrules is a cursor rule published in the GitHub repository nhadaututtheky/neural-memory (240 stars, last pushed 17d ago), licensed MIT. It adds 917 tokens to every session, about $0.0046 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.