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/auto-export)<a href="https://agentmods.dev/commands/sukinshetty/nemp-memory/auto-export"><img src="https://agentmods.dev/badge/commands/sukinshetty/nemp-memory/auto-export/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/auto-export"><img src="https://agentmods.dev/badge/commands/sukinshetty/nemp-memory/auto-export.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.00010 | $0.01543 |
| Opus 5.5 | $0.00004 | $0.00617 |
| Sonnet 5.5 | $0.00002 | $0.00309 |
| Haiku 4.5 | $0.00001 | $0.00154 |
Grade A, and why
auto-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 26d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/nemp:auto-export
Experimental configuration only: this repository has not established an automatic trigger from save/init/forget to provider export. Saving an enabled flag must not be reported as a working auto-export integration. Run a prototype export explicitly when testing.
Toggle automatic cross-provider export on or off, or configure export targets.
Usage
/nemp:auto-export on # Enable auto-export
/nemp:auto-export off # Disable auto-export
/nemp:auto-export status # Check current status (default)
/nemp:auto-export targets codex,cursor # Set export targets
/nemp:auto-export targets all # Export to all providers
/nemp:auto-export # Show status (same as status)
Arguments
on: Save the experimental auto-export preference; automatic hook execution requires validationoff: Disable automatic exportstatus: Show current auto-export status and targets (default if no argument)targets <list>: Set comma-separated export targets (codex,cursor,windsurf,all)
Instructions
When the user invokes /nemp:auto-export, follow these steps:
1. Parse Argument
Extract the action: on, off, status, or targets (default to status if empty).
For targets, also extract the comma-separated target list from the remainder of the argument.
2. Configuration File Location
Auto-export config is stored in: .nemp-pro/config.json
The autoExport section:
{
"autoExport": {
"enabled": false,
"targets": ["codex"],
"lastExport": null
}
}
3. Handle Actions
For on:
mkdir -p .nemp-pro
Read or create .nemp-pro/config.json, set autoExport.enabled = true, write back.
Read autoExport.targets from config to include in confirmation (default: ["codex"]).
Confirm:
Auto-export preference saved (experimental)
What will be auto-exported:
Targets: codex
Configured target files (automatic hook execution is unverified in this build):
- AGENTS.md (Codex CLI)
Run /nemp:auto-export targets codex,cursor,windsurf to change targets.
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.
- 26d ago Changed · +2 lines · +2 tokens per session 1c98b5b49f35
- 1mo ago First seen · 231 lines · 8 tokens per session scan A 6040e8943c2d
auto-export is a command published in the GitHub repository SukinShetty/Nemp-memory (139 stars, last pushed 24d ago), licensed MIT. It adds 10 tokens to every session and 1,543 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.
recall
Ask Honcho what it remembers about a topic from past sessions.
weekly
Weekly memory report — facts learned, procedures, repeated mistakes prevented.
setup
Configure mnemonic for proactive memory operations.
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).