A command that keeps a memory index in step with notes stored in Git. Git is a tool for tracking code changes; Git notes are extra information attached to those changes.

It is for incremental or full reindexing, checking consistency, repairing problems, and syncing with the remote repository through fetch, merge, and push.

It helps detect or fix differences between the index and the Git notes that store its information. It can preview changes or synchronize with a remote repository.

sync — Command by zircote

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/zircote/git-notes-memory/sync

Clone the repo

git clone --depth 1 https://github.com/zircote/git-notes-memory

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,400 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.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.02400
Opus 5	$0.00006	$0.01200
Sonnet 5	$0.00003	$0.00480
Haiku 4.5	$0.00001	$0.00240

Measured yesterday against content hash f7ec3b48c966, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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/sync.md · 316 lines

How it starts

The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.

<help_check>

Help Check

If $ARGUMENTS contains --help or -h:

Output this help and HALT (do not proceed further):

<help_output>

SYNC(1)                                              User Commands                                              SYNC(1)

NAME
    sync - Synchronize the memory index with git notes (local or remote)

SYNOPSIS
    /memory:sync [full|verify|repair|--remote] [--dry-run]

DESCRIPTION
    Synchronize the memory index with git notes. Supports both local index
    synchronization and remote sync with origin repository.

OPTIONS
    --help, -h                Show this help message
    --remote                  Sync with remote (fetch→merge→push workflow)
    --dry-run                 Preview changes without applying

MODES
    (default)                 Incremental local index sync
    full                      Complete reindex from git notes
    verify                    Check consistency without changes
    repair                    Fix detected inconsistencies
    --remote                  Sync with remote origin repository

EXAMPLES
    /memory:sync              Incremental local sync
    /memory:sync full         Full reindex
    /memory:sync verify       Check consistency
    /memory:sync repair       Fix inconsistencies
    /memory:sync --remote     Fetch, merge, and push with origin
    /memory:sync --dry-run    Preview what would change

SEE ALSO
    /memory:* for related commands

                                                                      SYNC(1)

</help_output>

After outputting help, HALT immediately. Do not proceed with command execution. </help_check>

/memory:sync - Synchronize Memory Index

Synchronize the local search index with git notes storage.

Your Task

You will help the user synchronize or repair the memory index.

Arguments format: $ARGUMENTS

Parse the arguments:

Check for --remote flag (triggers remote sync mode)
First positional argument is mode: incremental (default), full, verify, or repair
Extract --dry-run flag if present

Read the full file on GitHub · 316 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.

yesterday First seen · 316 lines · 13 tokens per session scan A f7ec3b48c966

Subscribe to this mod's changes

sync is a command published in the GitHub repository zircote/git-notes-memory (4 stars, last pushed 8mo ago), licensed MIT. It adds 13 tokens to every session and 2,400 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-31.

Git and workflow Languages Memory and context ai-tools claude-code claude-plugin embeddings git-notes mcp

sync

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Help Check

/memory:sync - Synchronize Memory Index

Your Task

What this file has done since we first saw it

Other commands, from other repositories

memory-graph

memory-recall

memory-status

assets

start

dashboard