log

A command that displays the audit history of a project's saved, retrieved, and deleted memories.

In plain words
What is it for?
Use it to inspect recent memory access, filter activity by agent, review reads and writes, or clear the access log.
Why use it?
It shows which actions happened, when they happened, which memory was involved, and which agent performed them.

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/log
Clone the repo
git clone --depth 1 https://github.com/SukinShetty/Nemp-memory
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 683 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.00011 $0.00683
Opus 5 $0.00005 $0.00342
Sonnet 5 $0.00002 $0.00137
Haiku 4.5 $0.00001 $0.00068

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

Security

Grade A, and why

log 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/log.md · 80 lines

How it starts

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

/nemp:log

View the memory access audit trail showing all reads, writes, and deletes.

Usage

/nemp:log # Show last 20 entries /nemp:log --tail 50 # Show last 50 entries /nemp:log --agent backend # Filter by agent name /nemp:log --clear # Clear the log

Instructions

1. Read Access Log

[ -f ".nemp/access.log" ] && tail -20 .nemp/access.log

If no log exists: 📋 No access log yet. The log tracks automatically when you use: /nemp:save → WRITE entries /nemp:recall → READ entries /nemp:forget → DELETE entries /nemp:init → INIT entries

2. Parse and Display

Default (last 20 entries): 📋 Nemp Access Log TIMESTAMP ACTION KEY AGENT 2026-02-11 14:30:00 INIT (6 memories) nemp-init 2026-02-11 14:32:15 READ auth-flow main 2026-02-11 14:35:00 WRITE api-design backend 2026-02-11 14:35:02 READ auth-flow frontend 2026-02-11 14:35:03 READ database tester 2026-02-11 14:40:00 DELETE old-api main Agents active: main, nemp-init, backend, frontend, tester

With --agent filter:

grep "agent=backend" .nemp/access.log

📋 Access Log — Agent: backend TIMESTAMP ACTION KEY 2026-02-11 14:35:00 WRITE api-design 2026-02-11 14:36:00 READ auth-flow 2 entries by "backend"

With --tail N:

tail -N .nemp/access.log

With --clear: Ask confirmation, then:

rm .nemp/access.log

Log Format

Each line: [ISO-TIMESTAMP] ACTION key=KEY agent=AGENT_NAME extra=INFO

Examples: [2026-02-11T14:30:00Z] WRITE key=auth-flow agent=nemp-init chars=45 [2026-02-11T14:32:15Z] READ key=auth-flow agent=main query=auth [2026-02-11T14:40:00Z] DELETE key=old-api agent=main [2026-02-11T14:30:00Z] INIT agent=nemp-init memories_saved=6

  • /nemp:list - List all memories
  • /nemp:save - Save a memory (creates WRITE log)
  • /nemp:recall - Recall a memory (creates READ log)

Read the full file on GitHub · 80 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 · 80 lines · 11 tokens per session scan A 15865ac48f80

Subscribe to this mod's changes

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