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-sync)<a href="https://agentmods.dev/commands/sukinshetty/nemp-memory/auto-sync"><img src="https://agentmods.dev/badge/commands/sukinshetty/nemp-memory/auto-sync/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-sync"><img src="https://agentmods.dev/badge/commands/sukinshetty/nemp-memory/auto-sync.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.00999 |
| Opus 5.5 | $0.00004 | $0.00400 |
| Sonnet 5.5 | $0.00002 | $0.00200 |
| Haiku 4.5 | $0.00001 | $0.00100 |
Grade A, and why
auto-sync 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 18d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/nemp:auto-sync
Toggle automatic syncing of memories to CLAUDE.md.
Usage
/nemp:auto-sync on # Enable auto-sync
/nemp:auto-sync off # Disable auto-sync
/nemp:auto-sync status # Check current status
/nemp:auto-sync # Show status (same as status)
Arguments
on: Enable automatic syncing to CLAUDE.md after memory changesoff: Disable automatic syncingstatus: Show current auto-sync status (default if no argument)
Instructions
When the user invokes /nemp:auto-sync, follow these steps:
1. Parse Argument
Extract the action: on, off, or status (default to status if empty).
2. Configuration File Location
Auto-sync config is stored in: .nemp/config.json
{
"autoSync": true
}
3. Handle Actions
For on:
mkdir -p .nemp
Read or create .nemp/config.json, set autoSync = true, write back.
Confirm:
Auto-sync ENABLED
What happens now:
- /nemp:save -> CLAUDE.md updates automatically
- /nemp:init -> CLAUDE.md updates automatically
- /nemp:forget -> CLAUDE.md updates automatically
These commands refresh the Nemp section when they complete successfully. Review the resulting diff; this is not a background file watcher.
For off:
Read .nemp/config.json, set autoSync = false, write back.
Confirm:
Auto-sync DISABLED
CLAUDE.md will not update automatically.
Run these manually when needed:
- /nemp:export (write memories to CLAUDE.md)
- /nemp:sync (two-way sync)
For status:
Read .nemp/config.json and display current state:
Auto-sync Status
Enabled: Yes/No
Config: .nemp/config.json
When enabled, these commands update CLAUDE.md:
- /nemp:save
- /nemp:init
- /nemp:forget
Commands:
/nemp:auto-sync on - Enable
/nemp:auto-sync off - Disable
4. Initialize Config (if not exists)
If .nemp/config.json doesn't exist, create it:
{
"autoSync": false
}
5. Read/Write Config
Use the Read tool to check for existing config, then Write tool to update it.
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.
- 18d ago Changed abd85354d855
- 1mo ago First seen · 166 lines · 10 tokens per session scan A 19715ce1e0e6
auto-sync is a command published in the GitHub repository SukinShetty/Nemp-memory (139 stars, last pushed 16d ago), licensed MIT. It adds 10 tokens to every session and 999 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.
lessons
Lists the feedback memories captured for the current project (and globally) — the "lessons" learned from user corrections.
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).