Borrowing it
Nothing to install: this file belongs to zotoio/CRUX-Compress. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zotoio/CRUX-Compress/main/.cursor/skills/crux-skill-memory-index/SKILL.mdgit clone --depth 1 https://github.com/zotoio/CRUX-CompressWrote 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/zotoio/crux-compress/crux-skill-memory-index)<a href="https://agentmods.dev/skills/zotoio/crux-compress/crux-skill-memory-index"><img src="https://agentmods.dev/badge/skills/zotoio/crux-compress/crux-skill-memory-index/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/zotoio/crux-compress/crux-skill-memory-index"><img src="https://agentmods.dev/badge/skills/zotoio/crux-compress/crux-skill-memory-index.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.01283 |
| Opus 5 | $0.00021 | $0.00642 |
| Sonnet 5 | $0.00008 | $0.00257 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
crux-skill-memory-index 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 12d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRUX Skill: Memory Index
Builds a prioritised index of all memory files by scanning the configured memory directories, joining with reference tracker data, and writing a sorted index to .crux/memory-index.yml.
When to Use
- After creating, updating, or deleting memories (post-CRUD housekeeping)
- During REM sleep / dream cycles to refresh the index
- When an agent needs to discover available memories sorted by priority
- After bulk operations that may have changed multiple memory files
Quick Start
# Rebuild the index (uses default config path)
python .cursor/skills/crux/crux-skill-memory-index/scripts/memory-index.py
# Rebuild with a custom config path
python .cursor/skills/crux/crux-skill-memory-index/scripts/memory-index.py --config path/to/config.json
# Post-dream rebuild (checks enableMemories flag, then rebuilds)
python .cursor/skills/crux/crux-skill-memory-index/scripts/post-dream.py
Post-Dream Rebuild
The post-dream.py script is a convenience wrapper invoked programmatically by the /crux-dream workflow after memory extraction or REM sleep completes. It:
- Checks
.crux/crux-memories.json— exits early ifenableMemoriesis not"true" - Calls
memory-index.pyto rebuild the index - The MCP server's file watcher detects the index timestamp change automatically
This script is not a Cursor event hook and is not registered in .cursor/hooks.json.
Configuration
All settings are read from .crux/crux-memories.json under the cruxMemories key:
| Setting | Default | Purpose |
|---|---|---|
storage.memoriesDir |
memories |
Root directory for base memories |
storage.agentMemoriesDir |
memories/agents |
Root for agent-scoped memories |
storage.indexFile |
.crux/memory-index.yml |
Output index file path |
referenceTracking.trackingDir |
.crux/reference-tracking |
Directory containing .refs.yml files |
typePriority |
[core, redflag, goal, learning, idea, archived] |
Sort order for memory types |
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.
- 12d ago First seen · 127 lines · 42 tokens per session scan A 43006e2d9f8a
crux-skill-memory-index is a skill published in the GitHub repository zotoio/CRUX-Compress (8 stars, last pushed 5d ago), licensed MIT. It adds 42 tokens to every session and 1,283 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-31.
Other skills, from other repositories
simplemem-skill
Store and retrieve conversation memories across sessions. Use when asked to 'remember this', 'save conversation', 'add to memory', 'what did we discuss about...', 'query memories', or 'import chat history'. Also use proactively to preserve important dialogue context and decisions.
[object Object]
Read, search, and open notes in the user's "{{GRAPHNAME}}" Reflect graph via the reflect CLI. Use when the user asks about their notes, daily notes, journal, or anything they may have written down in Reflect.
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
daily-journal
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…