memory-init

A setup helper for Engram, a project memory system that stores preferences, conversation history, and long-term notes. It creates the needed settings, memory files, and project integration.

In plain words
What is it for?
Use it when setting up or reconfiguring persistent memory for a project, including choosing a preset, language, search mode, or custom file names.
Why use it?
It removes the manual work of choosing a memory setup, creating files, and connecting Engram to the project. It also handles initializing missing settings or upgrading an existing setup.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/legacybridge-tech/claude-plugins/memory-init
Any agent
npx skills add legacybridge-tech/claude-plugins --skill memory-init
Clone the repo
git clone --depth 1 https://github.com/legacybridge-tech/claude-plugins

Made for: Claude Code, Codex.

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,544 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00054 $0.01544
Opus 5 $0.00027 $0.00772
Sonnet 5 $0.00011 $0.00309
Haiku 4.5 $0.00005 $0.00154

Measured 2d ago against content hash 3de2f8980759, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

memory-init 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 2d 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.

engram/skills/memory-init/SKILL.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory Init

Initialize the Engram memory system for the current project.

When to Use

Trigger this skill when:

  • The user explicitly asks to set up, initialize, or configure Engram / persistent memory
  • A memory-related skill (memory-remember, memory-recall, memory-status) is requested but .claude/memory-settings.json does not exist
  • The user re-runs init to upgrade an existing configuration (e.g. to change preset, language, or search_mode)

Workflow

1. Ask Preset Choice

Ask the user which preset they want:

  • personal-assistant — Daily life, preferences, habits, personal interactions
  • project-assistant — Codebase, architecture, tech decisions, team workflow
  • character-companion — Persona, relationship, story progression, emotional bonds
  • pair-programmer — AI self-learning, mistake tracking, user preference rules, collaboration patterns

Or offer custom configuration.

2. Ask File Name Customization

Show the default file names and ask if the user wants to change them:

memory_preferences.md    (User/Project/Character preferences)
memory_conversations.md  (Conversation history)
memory_longterm.md       (Long-term memories)

3. Ask Language Preference

  • en — English CLAUDE.md section (default)
  • zh — Chinese CLAUDE.md section

3.5 Ask Search Mode

  • strong — 回覆前預設先用 memory-recall 檢查一次記憶 / Check memories before responding by default
  • weak — 判斷話題可能涉及過去時才搜尋 / Search only when a topic may involve past context (default)

4. Create Configuration

Create .claude/memory-settings.json with the chosen settings:

{
  "preset": "<chosen-preset>",
  "files": {
    "preferences": "<preferences-filename>",
    "conversations": "<conversations-filename>",
    "longterm": "<longterm-filename>"
  },
  "language": "<en|zh>",
  "search_mode": "<strong|weak>"
}

5. Copy Preset Templates

Copy the template files from the plugin's templates/presets/<preset>/ directory to the project root. The plugin root is available via ${CLAUDE_PLUGIN_ROOT} or can be found by locating the engram plugin directory.

Read the full file on GitHub · 149 lines

Changes

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.

  1. 2d ago First seen · 149 lines · 54 tokens per session scan A 3de2f8980759

Subscribe to this mod's changes

memory-init is a skill published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 1,544 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens