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.
npx agentmods add commands/sukinshetty/nemp-memory/nemp-pro-exportgit 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/nemp-pro-export)<a href="https://agentmods.dev/commands/sukinshetty/nemp-memory/nemp-pro-export"><img src="https://agentmods.dev/badge/commands/sukinshetty/nemp-memory/nemp-pro-export.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.04209 |
| Opus 5 | $0.00008 | $0.02105 |
| Sonnet 5 | $0.00003 | $0.00842 |
| Haiku 4.5 | $0.00002 | $0.00421 |
Grade A, and why
nemp-pro-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 5d 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 — 553 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/nemp-pro:export
Export project memories to AI tool rule files used by Codex CLI (AGENTS.md), Cursor (.cursor/rules/nemp-memory.mdc), and Windsurf (.windsurfrules). Keeps your entire AI toolchain in sync from a single source of truth: .nemp/memories.json.
Usage
/nemp-pro:export --codex # Generate AGENTS.md for Codex CLI
/nemp-pro:export --cursor # Generate .cursor/rules/nemp-memory.mdc for Cursor
/nemp-pro:export --windsurf # Generate .windsurfrules for Windsurf
/nemp-pro:export --all # Generate all three + sync CLAUDE.md
/nemp-pro:export --status # Check which export files exist
Arguments
--codex(optional): Export toAGENTS.mdin project root (Codex CLI format)--cursor(optional): Export to.cursor/rules/nemp-memory.mdc(MDC frontmatter format)--windsurf(optional): Export to.windsurfrulesin project root (plain markdown)--all(optional): Run all three exports and trigger CLAUDE.md sync--status(optional): Report which export files exist and their last modified timestamps
Instructions
When the user invokes /nemp-pro:export, follow these steps:
Step 1: Parse Arguments
Extract the subcommand from the user's input:
--codex → Export to AGENTS.md
--cursor → Export to .cursor/rules/nemp-memory.mdc
--windsurf → Export to .windsurfrules
--all → Run all three exports + CLAUDE.md sync
--status → Show export file status
(no args) → Show Usage block above and stop
If no argument is provided or the argument is unrecognised, display the Usage block above and stop.
Memory Reading Logic (used by all export subcommands)
Before generating any export file, perform these steps to load and prepare memories. This logic is shared by --codex, --cursor, --windsurf, and --all.
Step 2: Read memories.json
Read .nemp/memories.json using the Read tool:
[ -f ".nemp/memories.json" ] && cat .nemp/memories.json
If the file does not exist, stop and show:
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.
- 5d ago First seen · 553 lines · 16 tokens per session scan A 7320441003c9
nemp-pro-export is a command published in the GitHub repository SukinShetty/Nemp-memory (128 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 4,209 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.
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.
remember
Log current finding or successful pattern to hunt memory. Auto-fills from /validate output if available. Usage: /remember.
encode-repo
Bootstrap a repository into Forgetful's knowledge base.
memory-search
Search memories semantically using Forgetful.
memory-list
List recent memories from Forgetful.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.