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/sync)<a href="https://agentmods.dev/commands/sukinshetty/nemp-memory/sync"><img src="https://agentmods.dev/badge/commands/sukinshetty/nemp-memory/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/sync"><img src="https://agentmods.dev/badge/commands/sukinshetty/nemp-memory/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.00012 | $0.03290 |
| Opus 5.5 | $0.00005 | $0.01316 |
| Sonnet 5.5 | $0.00002 | $0.00658 |
| Haiku 4.5 | $0.00001 | $0.00329 |
Grade A, and why
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 1mo 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 — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/nemp:sync
Two-way bridge between Nemp Memory and CLAUDE.md. Import user-written context from CLAUDE.md into Nemp, detect conflicts with actual project state, and update the Nemp section.
Usage
/nemp:sync # Full two-way sync
/nemp:sync --import-only # Only read from CLAUDE.md into Nemp, don't write back
/nemp:sync --export-only # Same as /nemp:export
/nemp:sync --check # Only detect conflicts, don't change anything
Arguments
--import-only(optional): Only import from CLAUDE.md to Nemp memories, skip export--export-only(optional): Only export Nemp memories to CLAUDE.md (same as /nemp:export)--check(optional): Dry run - detect conflicts without making any changes
Instructions
When the user invokes /nemp:sync, follow these steps:
Step 1: Parse Arguments
Extract the mode from arguments:
- No arguments → full sync (import + conflict check + export)
--import-only→ only import from CLAUDE.md--export-only→ only export to CLAUDE.md--check→ only detect conflicts, no changes
Step 2: Read CLAUDE.md
Check if CLAUDE.md exists and read its contents:
[ -f "CLAUDE.md" ] && cat CLAUDE.md || echo "CLAUDE_MD_NOT_FOUND"
If CLAUDE.md doesn't exist:
⚠️ No CLAUDE.md found.
Nothing to import. You can:
/nemp:export - Create CLAUDE.md from Nemp memories
/nemp:init - Auto-detect project stack first
Step 3: Parse CLAUDE.md Content
Split CLAUDE.md into two parts:
Nemp Section (SKIP):
- Starts with:
## Project Context (via Nemp Memory) - Ends at: next
##heading, or---on its own line, or end of file - This is Nemp's own output — do NOT re-import it
User Content (IMPORT):
- Everything OUTSIDE the Nemp section
- This includes manually written context, rules, preferences, architecture notes
Step 4: Extract Importable Context
Scan the user content for importable information. Look for patterns like:
| Pattern | Memory Key |
|---|---|
| "Tech stack:", "Stack:", "We use" | stack |
| "Framework:", "Built with" | framework |
| "Database:", "DB:", "ORM:" | database |
| "Auth:", "Authentication:" | auth |
| "Styling:", "CSS:", "UI:" | styling |
| "Testing:", "Tests:" | testing |
| "Package manager:", "Use npm/pnpm/yarn/bun" | package-manager |
| "Architecture:", "Structure:" | architecture |
| "Rules:", "Conventions:", "Preferences:" | conventions |
| "API:", "Endpoints:" | api |
| Bullet points under headings | Extract as relevant memory |
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.
- 1mo ago First seen · 432 lines · 12 tokens per session scan A f4c6922cb55e
sync is a command published in the GitHub repository SukinShetty/Nemp-memory (139 stars, last pushed 13d ago), licensed MIT. It adds 12 tokens to every session and 3,290 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.
setup
Configure mnemonic for proactive memory operations.
lessons
Lists the feedback memories captured for the current project (and globally) — the "lessons" learned from user corrections.
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).