auto-sync

A command for turning automatic updates to CLAUDE.md on or off when Nemp memories change.

In plain words
What is it for?
Use it to enable, disable, or check automatic syncing in a project's .nemp/config.json file.
Why use it?
It removes the need to update that file manually after saving, initializing, or deleting memories.

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/auto-sync
Clone the repo
git clone --depth 1 https://github.com/SukinShetty/Nemp-memory
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 975 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.00010 $0.00975
Opus 5 $0.00005 $0.00487
Sonnet 5 $0.00002 $0.00195
Haiku 4.5 $0.00001 $0.00097

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

Security

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 3d 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/auto-sync.md · 166 lines

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 changes
  • off: Disable automatic syncing
  • status: 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

CLAUDE.md will always stay in sync with your memories.

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.

Reading config:

[ -f ".nemp/config.json" ] && cat .nemp/config.json

Read the full file on GitHub · 166 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. 3d ago First seen · 166 lines · 10 tokens per session scan A 19715ce1e0e6

Subscribe to this mod's changes

auto-sync is a command published in the GitHub repository SukinShetty/Nemp-memory (128 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 975 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.