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 skills add adamwang99/NEUTRON-EVO-OS --skill memorygit clone --depth 1 https://github.com/adamwang99/NEUTRON-EVO-OSWrote 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/adamwang99/neutron-evo-os/memory)<a href="https://agentmods.dev/skills/adamwang99/neutron-evo-os/memory"><img src="https://agentmods.dev/badge/skills/adamwang99/neutron-evo-os/memory/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/skills/adamwang99/neutron-evo-os/memory"><img src="https://agentmods.dev/badge/skills/adamwang99/neutron-evo-os/memory.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.00001 | $0.00668 |
| Opus 5.5 | $0.00000 | $0.00267 |
| Sonnet 5.5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
memory 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 2mo 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution Logic
Purpose
Manage long-term memory, daily logs, and Memory 2.0 (Dream Cycle: pruning + distillation) for NEUTRON EVO OS.
CLI Integration
Use the memoryos CLI for session lifecycle management:
memoryos wake— recover session context at startmemoryos remember "note" [--category <type>]— capture structured memoriesmemoryos search "query"— search across all memoriesmemoryos status— show MemoryOS statisticsmemoryos sleep "summary" --next "next task"— save session checkpoint
Memory Architecture
memory/
├── YYYY-MM-DD.md → Daily logs (append-only)
├── archived/ → Archived user data (NEVER DELETE)
│ └── *.log → Timestamped archived logs
├── cookbooks/ → Distilled knowledge summaries
│ └── *.md → Compressed topic summaries
└── learned/ → Learned skill patterns (via engine)
Daily Log Protocol
- Session start: Read
memory/YYYY-MM-DD.md(today's log) - Session end: Append session summary to
memory/YYYY-MM-DD.md - Format: ISO timestamp + task + outcome + key learnings
Log Entry Format
## [HH:MM] — Task: <brief description>
- Action: <what was done>
- Outcome: <result>
- CI delta: <+/-N>
- Notes: <anything worth remembering>
Archive Protocol (CRITICAL)
- User data: ALWAYS move to
/memory/archived/— never hard delete - System noise:
.tmp,.cachefiles can be pruned after 3 days without references - Format:
YYYY-MM-DD_HH-MM-SS_original-name.ext - Archive before any modification or deletion operation
Dream Cycle (Memory 2.0)
Triggered by Smart Observer when work settles (30s debounce):
- Archive Phase: Copy current logs to
/memory/archived/with timestamp - Prune Phase: Remove
.tmp/.cachefiles older than 3 days - Distill Phase: Compress repetitive patterns into Cookbooks
- Update: Set
last_dreamin this SKILL.md header
Retrieval
- Daily logs:
memory/YYYY-MM-DD.md - Topic search: grep over
memory/directory - Cookbooks:
memory/cookbooks/<topic>.md - Archived:
memory/archived/*.log
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 74 lines · 1 tokens per session scan A 18dc713d2328
memory is a skill published in the GitHub repository adamwang99/NEUTRON-EVO-OS (20 stars, last pushed 6mo ago), licensed MIT. It adds 1 tokens to every session and 668 once invoked, about $0.0000 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-30.
Other skills, from other repositories
metago-expert-knowledge-crystal-curator
A Chinese-language system for managing short-term conversation notes, long-term stored knowledge, and reusable skills. It covers saving, finding, updating, and retiring this information over time.
metago-developer-response
A response procedure for handling developer corrections or criticism. It calls for checking the relevant evidence, finding the cause of an error, correcting the answer, and recording the lesson for future cases.
metago-memory-manage
A Chinese-language framework for managing knowledge and memory in four layers: facts, stored information, learned patterns and harder-to-explain judgement.
soul-migration
SOUL.md management and soul preservation across model architectures and system deployments.
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…