list

A command for listing saved project and global memory entries. These memories are stored notes that an agent can reuse across tasks.

In plain words
What is it for?
It is for showing memory keys, their source, update time, agent, and a short preview, with options to list project, global, or all memories.
Why use it?
It makes remembered settings and project knowledge visible instead of requiring you to inspect memory files manually.

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/list
Clone the repo
git clone --depth 1 https://github.com/SukinShetty/Nemp-memory
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 770 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.00005 $0.00770
Opus 5 $0.00003 $0.00385
Sonnet 5 $0.00001 $0.00154
Haiku 4.5 $0.00001 $0.00077

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

Security

Grade A, and why

list 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/list.md · 98 lines

How it starts

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

/nemp:list

List all saved memory keys.

Usage

/nemp:list /nemp:list --global # Show only global memories /nemp:list --project # Show only project memories /nemp:list --all # Show both (default)

Instructions

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

1. Load Memories from Both Locations

# Check and read project memories
[ -f ".nemp/memories.json" ] && cat .nemp/memories.json

# Check and read global memories
[ -f "$HOME/.nemp/memories.json" ] && cat $HOME/.nemp/memories.json

2. Format Output

Group memories by source and display with agent tracking: 📚 Nemp Memory Index ── Project Memories (.nemp/memories.json) ────────────────── KEY AGENT UPDATED PREVIEW auth-flow nemp-init 2026-02-11 NextAuth.js with JWT... db-config backend 2026-02-11 PostgreSQL via Prisma... api-design main 2026-02-10 RESTful, versioned... Total: 3 memories ── Global Memories (~/.nemp/memories.json) ────────────────── KEY AGENT UPDATED PREVIEW preferred-editor main 2026-02-08 VS Code with Vim... Total: 1 memory ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Total: 4 memories across all sources

3. Update MEMORY.md Index

After listing, regenerate .nemp/MEMORY.md to keep the index current.

# Nemp Memory Index

> Auto-generated. Last updated: [YYYY-MM-DD HH:MM]

## Stored Memories

| Key | Preview | Agent | Updated |
|-----|---------|-------|---------|
| auth-flow | NextAuth.js with JWT... | nemp-init | 2026-02-11 |
| db-config | PostgreSQL via Prisma... | backend | 2026-02-11 |

## Files

| File | Purpose |
|------|---------|
| `memories.json` | All stored memories |
| `access.log` | Read/write audit trail |
| `config.json` | Plugin configuration |
| `MEMORY.md` | This index file |

4. Empty State

If no memories exist: 📚 Nemp Memory Index No memories saved yet. Get started: /nemp:save - Save your first memory Examples: /nemp:save user-prefers-typescript User prefers TypeScript over JavaScript /nemp:save project-uses-nextjs This project uses Next.js 14 with App Router

Read the full file on GitHub · 98 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 · 98 lines · 5 tokens per session scan A 1fd65eb541f0

Subscribe to this mod's changes

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