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/daily-notes)<a href="https://agentmods.dev/rules/lezards/neuron-vault-kit/daily-notes"><img src="https://agentmods.dev/badge/rules/lezards/neuron-vault-kit/daily-notes/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/daily-notes"><img src="https://agentmods.dev/badge/rules/lezards/neuron-vault-kit/daily-notes.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.00018 | $0.00296 |
| Opus 5.5 | $0.00007 | $0.00118 |
| Sonnet 5.5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
daily-notes 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
Daily notes
Daily notes são memórias datadas em neuron-vault/daily/YYYY-MM-DD.md.
Quando criar/atualizar
- Decisão tomada hoje que muda direção do projeto
- Incidente do dia com root cause identificado
- Continuação de trabalho ("amanhã continuamos em X")
- Reunião decisiva com outcome importante
Quando NÃO criar
- Tarefas pequenas/rotineiras
- Logs de comandos
- Coisas que vão virar neuron permanente — escreva direto em
neurons/
Formato
# YYYY-MM-DD
## Decidido
- [decisão 1] — [contexto curto]
## Eventos
- [evento 1] — [outcome]
## Para amanhã
- [item 1]
Promoção
Se a daily note tem informação útil em 30+ dias (regra durável, decisão arquitetural), promova pra neurons/<tipo>-<slug>.md e mantenha apenas referência curta na daily.
Recuperação pós-quebra de contexto
Se o usuário diz "perdi o chat", "PC reiniciou", "tava conversando contigo": liste e leia as últimas 2-3 dailies pra reconstruir contexto.
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 · 45 lines · 18 tokens per session scan A e44a0c0e431a
daily-notes is a cursor rule published in the GitHub repository lezards/neuron-vault-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 296 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.