save

A command for saving a short key-and-value note in persistent memory. It cleans up filler and repeated wording while preserving technical terms, file paths, package names, and version numbers.

In plain words
What is it for?
Use /nemp:save to record decisions, configuration details, preferences, authentication choices, or other project facts for future recall.
Why use it?
It keeps important project information available across sessions without storing unnecessary wording. A consistent key makes the note easier to retrieve later.

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/save
Clone the repo
git clone --depth 1 https://github.com/SukinShetty/Nemp-memory
Per session 9 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,467 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.00009 $0.02467
Opus 5 $0.00005 $0.01234
Sonnet 5 $0.00002 $0.00493
Haiku 4.5 $0.00001 $0.00247

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

Security

Grade A, and why

save 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/save.md · 269 lines

How it starts

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

Save a memory to persistent storage.

Usage

/nemp:save

Arguments

  • key: A unique identifier for this memory (use kebab-case, e.g., user-prefers-bun, auth-flow-jwt)
  • value: The content to remember (string, can be multi-word)

Instructions

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

1. Parse Arguments

Extract the key (first argument) and value (everything after the key).

2. Compress Value (Token Optimization)

IMPORTANT: Always compress the value before storing to minimize token usage.

Apply these compression rules:

  • Remove filler words: "basically", "essentially", "the thing is", "it's worth noting"
  • Remove redundant phrases: "in order to" → "to", "due to the fact that" → "because"
  • Collapse whitespace and trim
  • Keep under 200 characters when possible — summarize longer values to their essential facts
  • Preserve all technical terms, file paths, package names, and version numbers exactly

Example compressions: BEFORE: "We decided to use NextAuth.js for authentication because it integrates well with Next.js and supports multiple providers including Google and GitHub OAuth" AFTER: "NextAuth.js auth with Google + GitHub OAuth providers" BEFORE: "The database is PostgreSQL and we access it through the Prisma ORM which handles all our migrations and schema management" AFTER: "PostgreSQL via Prisma ORM (migrations + schema)"

3. Determine Storage Location

  • Global storage: ~/.nemp/memories.json (cross-project memories)
  • Project storage: .nemp/memories.json in current working directory (project-specific)

Default to project storage if inside a git repository, otherwise use global storage.

3. Read or Initialize Storage

Use Bash to check if the storage file exists and read it:

# For project storage
if [ -f ".nemp/memories.json" ]; then
  cat .nemp/memories.json
else
  mkdir -p .nemp && echo '{}' > .nemp/memories.json
fi

5. Detect Agent Identity

Determine who is saving this memory:

echo "${CLAUDE_AGENT_NAME:-main}"

Read the full file on GitHub · 269 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 · 269 lines · 9 tokens per session scan A 362a707566a5

Subscribe to this mod's changes

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