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.
git clone --depth 1 https://github.com/SukinShetty/Nemp-memoryWrote 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/commands/sukinshetty/nemp-memory/save)<a href="https://agentmods.dev/commands/sukinshetty/nemp-memory/save"><img src="https://agentmods.dev/badge/commands/sukinshetty/nemp-memory/save/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/commands/sukinshetty/nemp-memory/save"><img src="https://agentmods.dev/badge/commands/sukinshetty/nemp-memory/save.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.00009 | $0.02482 |
| Opus 5.5 | $0.00004 | $0.00993 |
| Sonnet 5.5 | $0.00002 | $0.00496 |
| Haiku 4.5 | $0.00001 | $0.00248 |
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 15d 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 — 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.jsonin 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}"
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.
- 15d ago Changed 769b6030e794
- 1mo ago First seen · 269 lines · 9 tokens per session scan A 362a707566a5
save is a command published in the GitHub repository SukinShetty/Nemp-memory (139 stars, last pushed 13d ago), licensed MIT. It adds 9 tokens to every session and 2,482 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 commands, from other repositories
memory-gc
Inspect or rotate hunt-memory JSONL files (audit.jsonl, patterns.jsonl, journal.jsonl). Caps file size and keeps N rotated backups so memory does not grow unbounded.
iai-directive
Record, list, or remove a standing order the user typed themselves.
weekly
Weekly memory report — facts learned, procedures, repeated mistakes prevented.
setup
Configure mnemonic for proactive memory operations.
lessons
Lists the feedback memories captured for the current project (and globally) — the "lessons" learned from user corrections.
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).