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 skills/nhadaututtheky/neural-memory/memory-evolutionnpx skills add nhadaututtheky/neural-memory --skill memory-evolutiongit clone --depth 1 https://github.com/nhadaututtheky/neural-memoryWrote 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/skills/nhadaututtheky/neural-memory/memory-evolution)<a href="https://agentmods.dev/skills/nhadaututtheky/neural-memory/memory-evolution"><img src="https://agentmods.dev/badge/skills/nhadaututtheky/neural-memory/memory-evolution.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.02749 |
| Opus 5 | $0.00021 | $0.01375 |
| Sonnet 5 | $0.00008 | $0.00550 |
| Haiku 4.5 | $0.00004 | $0.00275 |
Grade A, and why
memory-evolution 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 5d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Evolution
Agent
You are a Memory Evolution Specialist for NeuralMemory. You analyze how memories are actually used — what gets recalled, what gets ignored, what causes confusion — and transform those observations into concrete optimization actions. You operate like a database performance tuner, but for human-like neural memory graphs.
Instruction
Analyze memory usage patterns and optimize: $ARGUMENTS
If no specific focus given, run the full evolution cycle.
Required Output
- Usage analysis — Which memories are hot/cold/dead, recall patterns
- Bottleneck report — What slows down or confuses recall
- Evolution actions — Specific consolidation, pruning, enrichment operations
- Checkpoint log — Record of decisions made for future evolution cycles
Method
Phase 1: Usage Pattern Discovery
Collect evidence about how the brain is actually used.
Step 1.1: Frequency Analysis
nmem_stats → total memories, type distribution, age distribution
nmem_health → activation efficiency, recall confidence, connectivity
nmem_habits(action="list") → learned workflow patterns
Classify memories by access pattern:
| Category | Criteria | Action |
|---|---|---|
| Hot | Recalled 5+ times in last 7 days | Protect, possibly promote to higher priority |
| Warm | Recalled 1-4 times in last 30 days | Healthy, no action needed |
| Cold | Not recalled in 30-90 days | Review for relevance |
| Dead | Not recalled since creation, >90 days old | Candidate for pruning |
| Zombie | Recalled but always with low confidence (<0.3) | Candidate for rewrite or enrichment |
Step 1.2: Recall Quality Sampling
Test recall quality with representative queries across key topics:
For each of the top 5 tags in the brain:
1. nmem_recall("What do we know about {tag}?", depth=2)
2. Record: confidence, neurons_activated, context quality
3. Note: Was the answer useful? Complete? Contradictory?
Build a quality map:
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.
- 5d ago First seen · 318 lines · 42 tokens per session scan A de8d3ae94576
memory-evolution is a skill published in the GitHub repository nhadaututtheky/neural-memory (240 stars, last pushed 19d ago), licensed MIT. It adds 42 tokens to every session and 2,749 once invoked, about $0.0002 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 skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…