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/lezards/neuron-vault-kitWrote 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/lezards/neuron-vault-kit/neuron-vault-write)<a href="https://agentmods.dev/rules/lezards/neuron-vault-kit/neuron-vault-write"><img src="https://agentmods.dev/badge/rules/lezards/neuron-vault-kit/neuron-vault-write/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/lezards/neuron-vault-kit/neuron-vault-write"><img src="https://agentmods.dev/badge/rules/lezards/neuron-vault-kit/neuron-vault-write.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.00013 | $0.00501 |
| Opus 5.5 | $0.00005 | $0.00200 |
| Sonnet 5.5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
neuron-vault-write 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
NeuronVault — escrita
Quando aprender algo que vai ser útil em conversas futuras, salve como neuron.
Quando salvar
| Sinal | Tipo |
|---|---|
| Usuário corrige seu approach ("não, não faz X") | feedback |
| Usuário aprova uma escolha não-óbvia ("isso, exatamente assim") | feedback |
| Você aprende role/stack/preferência do usuário | user |
| Decisão de projeto, deadline, motivação não-óbvia | project |
| Sistema externo importante (Linear, Grafana, etc) | reference |
| Procedimento repetitivo que o usuário descreveu | skill |
Quando NÃO salvar
- Padrões de código (descobre lendo o repo)
- História do git (já está em
git log) - Detalhes ephemeral da conversa atual
- Algo já documentado em
CLAUDE.mdou nas próprias Rules
Formato
Crie arquivo em neuron-vault/neurons/<tipo>-<slug>.md com frontmatter:
---
name: <título curto>
description: <uma linha — futuro Claude usa pra decidir relevância>
type: <user | feedback | project | reference | skill>
---
Para feedback e project, use estrutura Why/How to apply:
[a regra ou fato em uma frase]
**Why:** [motivo concreto — incidente, restrição, preferência]
**How to apply:** [quando essa regra entra em jogo]
Atualize o índice
Sempre que cria/atualiza/remove um neuron, edite neuron-vault/MEMORY.md adicionando/ajustando/removendo a linha:
- [Título](neurons/arquivo.md) — descrição em ≤150 caracteres
Não duplique
Antes de criar neuron novo, busque em MEMORY.md se já existe um sobre o mesmo tema. Se sim, atualize o existente em vez de criar duplicata.
Quando memória estiver obsoleta
Se você lê uma memória e o código contradiz, ou usuário corrige a memória, atualize ou remova — não acumule erro.
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 · 64 lines · 13 tokens per session scan A 62ccd3ef5643
neuron-vault-write is a cursor rule published in the GitHub repository lezards/neuron-vault-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 501 once invoked, about $0.0001 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
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Search dreamd at the start of a task and quote a hit. Append when the user corrects you or states a decision.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.