export

A command that exports project memories from a memory file into CLAUDE.md, a Markdown file used to give coding assistants project instructions and context.

In plain words
What is it for?
Appending or updating the Nemp memory section in CLAUDE.md, or replacing the entire file with the stored memories.
Why use it?
It saves you from manually copying stored project knowledge into the assistant’s instruction file. You can update only the memory section or replace the file’s contents.

Command

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 commands/sukinshetty/nemp-memory/export
Clone the repo
git clone --depth 1 https://github.com/SukinShetty/Nemp-memory
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,193 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.00007 $0.02193
Opus 5 $0.00003 $0.01097
Sonnet 5 $0.00001 $0.00439
Haiku 4.5 $0.00001 $0.00219

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

Security

Grade A, and why

export 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.

commands/export.md · 291 lines

How it starts

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

/nemp:export

Export all project memories to CLAUDE.md. Use --replace to overwrite the entire file, or run without flags to append/update the Nemp section only.

Usage

/nemp:export           # Append or update Nemp section in CLAUDE.md
/nemp:export --replace # Replace entire CLAUDE.md with Nemp content only

Arguments

  • (no args): Append or update the Nemp section in CLAUDE.md
  • --replace: Replace the entire CLAUDE.md instead of appending/updating

Instructions

When the user invokes /nemp:export, follow these steps:

Step 1: Parse Arguments

Identify which flag (if any) the user provided:

(no args)    → Export to CLAUDE.md (append/update)
--replace    → Export to CLAUDE.md (full replace)

If the argument is unrecognised, display the Usage block above and stop.


Memory Loading (shared by all export paths)

Before generating any export file, perform these steps to load and prepare memories.

Step 2: Read memories.json

Read .nemp/memories.json:

[ -f ".nemp/memories.json" ] && cat .nemp/memories.json

If the file does not exist, stop and show:

❌ No memories to export.

Save some memories first:
  /nemp:save stack Next.js 15 with TypeScript
  /nemp:init  (auto-detect project stack)

Step 3: Parse Format (with Backward Compatibility)

The file may use either format:

New array format:

{
  "memories": [
    {
      "key": "version",
      "value": "0.3.0",
      "created": "2026-02-26T16:00:00.000Z",
      "updated": "2026-02-26T16:00:00.000Z",
      "tags": ["auto-detected"],
      "type": "fact",
      "vitality": { "state": "active" }
    }
  ]
}

Legacy flat-object format:

{
  "stack": { "value": "Next.js", "created": "...", "updated": "..." },
  "auth":  { "value": "NextAuth", "created": "...", "updated": "..." }
}

If the parsed JSON does not have a memories array, treat each top-level key as a memory entry with:

key      = the JSON key name
value    = entry.value
created  = entry.created
updated  = entry.updated
type     = entry.type (if present, else undefined)
vitality = entry.vitality (if present, else undefined)

Read the full file on GitHub · 291 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 · 291 lines · 7 tokens per session scan A c9b74d1ad4a8

Subscribe to this mod's changes

export is a command published in the GitHub repository SukinShetty/Nemp-memory (128 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 2,193 once invoked, about $0.0000 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.