memsync: Instructions file for Claude Code

CLAUDE.md

memsync CLAUDE.md is an instructions file for Claude Code from EdgeCaser/memsync. It costs 894 tokens per session, scanned A, original, MIT.

Project instructions for memsync, a command-line tool that keeps Claude Code’s shared memory file synchronized across computers using existing cloud drives.

In plain words
What is it for?
Use them as a starting guide when building or modifying memsync.
Why use it?
They give the agent the project structure, design decisions, existing code, and known risks it needs before changing the code.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is EdgeCaser/memsync's own configuration. It tells Claude Code how to work on memsync itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything memsync configures →

Reuse

Borrowing it

Nothing to install: this file belongs to EdgeCaser/memsync. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/EdgeCaser/memsync/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/EdgeCaser/memsync

Made for: Claude Code.

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

agentmods badge for memsync CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/edgecaser/memsync/claude-md/github.svg)](https://agentmods.dev/instructions/edgecaser/memsync/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/edgecaser/memsync/claude-md"><img src="https://agentmods.dev/badge/instructions/edgecaser/memsync/claude-md/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.

agentmods 80×15 button for memsync CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/edgecaser/memsync/claude-md"><img src="https://agentmods.dev/badge/instructions/edgecaser/memsync/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 894 This file is loaded in full into every session.
When invoked 894 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00894 $0.00894
Opus 5.5 $0.00358 $0.00358
Sonnet 5.5 $0.00179 $0.00179
Haiku 4.5 $0.00089 $0.00089

Measured 2mo ago against content hash b32360408611, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

memsync CLAUDE.md 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 2mo 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.

CLAUDE.md · 93 lines

How it starts

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

memsync — Project Context for Claude Code

You are building memsync, a cross-platform CLI tool that maintains a global identity-layer memory file for Claude Code users, synced across machines via cloud storage they already have (OneDrive, iCloud Drive, Google Drive).

This document is your entry point. Read all linked documents before writing any code.


Document map

File What it contains
CLAUDE.md This file — start here
ARCHITECTURE.md Full system design, module map, data flow
PROVIDERS.md Provider plugin system — BaseProvider ABC, all three implementations
CONFIG.md Config file design, schema, platform paths
COMMANDS.md Every CLI command — args, behavior, edge cases
EXISTING_CODE.md Working prototype code — use this as the base, not a reference
PITFALLS.md Known issues, trust boundaries, things that have already gone wrong
REPO.md Repository structure, CI, PyPI, GitHub conventions
STYLE.md Code style, naming conventions, what good looks like here

Read them in this order:

  1. ARCHITECTURE.md — understand the shape of the system
  2. EXISTING_CODE.md — understand what already works
  3. PROVIDERS.md — the most important new piece
  4. CONFIG.md — feeds into everything
  5. PITFALLS.md — read before touching sync.py or providers
  6. COMMANDS.md, REPO.md, STYLE.md — as needed

What this project is

memsync solves a specific problem: Claude Code has no memory between sessions. The standard fix is ~/.claude/CLAUDE.md, but it drifts, bloats, and doesn't sync across machines.

memsync maintains one canonical GLOBAL_MEMORY.md in your cloud sync folder. At session start, Claude Code reads it via a symlink (Mac/Linux) or copy (Windows) at ~/.claude/CLAUDE.md. After meaningful sessions, the user runs memsync refresh --notes "..." and the Claude API merges the notes in.

This is the identity layer — who the user is, what they're working on, standing preferences. Not project docs. Not cold storage. Not a knowledge base.

Read the full file on GitHub · 93 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. 2mo ago First seen · 93 lines · 894 tokens per session scan A b32360408611

Subscribe to this mod's changes

memsync CLAUDE.md is an instructions file published in the GitHub repository EdgeCaser/memsync (2 stars, last pushed 11d ago), licensed MIT. It adds 894 tokens to every session, about $0.0036 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-31.

Related

memsync CLAUDE.md compared with instructions from other repositories

memsync CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
memsync CLAUDE.mdEdgeCaser/memsyncInstructions file211d agoMITA894Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode