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/lezards/neuron-vault-kit/neuron-vault-readgit clone --depth 1 https://github.com/lezards/neuron-vault-kitWhat 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.00363 | $0.00363 |
| Opus 5 | $0.00181 | $0.00181 |
| Sonnet 5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
neuron-vault-read 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.
What it actually says
NeuronVault — leitura
Este projeto usa NeuronVault, um sistema de memória persistente baseado em arquivos .md.
Antes de responder ao usuário
- Sempre leia
neuron-vault/MEMORY.md— é o índice de memórias. - Se uma entrada do índice é relevante ao tópico atual, leia o neuron completo em
neuron-vault/neurons/<arquivo>.md. - Se houver daily notes recentes em
neuron-vault/daily/(últimos 2-3 dias), leia para contexto temporal.
Tipos de memória
| Tipo | Conteúdo |
|---|---|
user |
Quem é o usuário, role, stack, preferências |
feedback |
Correções/aprovações que ele deu — siga essas regras |
project |
Estado de iniciativas, decisões, deadlines |
reference |
Onde achar info em sistemas externos |
skill |
Procedimentos repetitivos que o usuário documentou |
Comportamento esperado
- Aplique
feedbackautomaticamente sem repetir guidance que o usuário já deu. - Use
userprofile pra calibrar profundidade técnica e tom. - Cite
referencequando relevante ("vê o ticket no Linear INGEST"). - Trate
projectcomo contexto vivo — fatos podem ter mudado, verifique no código quando crítico.
Quando memória conflita com código atual
Memórias podem ficar obsoletas. Se um neuron diz "função X faz Y" mas você lê o código e Y mudou, confie no código e atualize/remova o neuron stale.
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 · 36 lines · 363 tokens per session scan A 3e99e66f5b08
neuron-vault-read is a cursor rule published in the GitHub repository lezards/neuron-vault-kit (2 stars, last pushed 15d ago), licensed MIT. It adds 363 tokens to every session, about $0.0018 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-31.
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.