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.
npx agentmods add skills/letta-ai/letta-code/syncing-memory-filesystemnpx skills add letta-ai/letta-code --skill syncing-memory-filesystemgit clone --depth 1 https://github.com/letta-ai/letta-codeWrote 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/skills/letta-ai/letta-code/syncing-memory-filesystem)<a href="https://agentmods.dev/skills/letta-ai/letta-code/syncing-memory-filesystem"><img src="https://agentmods.dev/badge/skills/letta-ai/letta-code/syncing-memory-filesystem.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.01608 |
| Opus 5 | $0.00021 | $0.00804 |
| Sonnet 5 | $0.00008 | $0.00322 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
syncing-memory-filesystem 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 4d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MemFS Repository Repair
Use this skill only when the Git repository behind an agent's memory is not setting up or syncing correctly. For ordinary memory reads and edits, use the memory files or the memory tools without loading this skill.
Current Model
MemFS is a Git repository projected onto the computer where the agent is
running. $MEMORY_DIR is the repository root. There is no second memory/
directory inside it.
The repository can use either memory layout. Inspect its current tree and the memory rules in the system prompt before editing files:
Root layout Existing layout
$MEMORY_DIR/ $MEMORY_DIR/
├── MEMORY.md # root index ├── system/ # in-context memory
├── persona.md # core memory ├── reference/ # deferred memory
├── <topic>/ └── skills/ # agent-owned skills
│ └── MEMORY.md # child index
└── skills/ # agent-owned skills
Cloud-backed agents have a hosted MemFS remote. Local-backend agents keep a local-only Git repository and do not need a remote or cloud credentials.
The memory tools commit their changes. After each turn, the harness pushes
clean committed changes for cloud-backed agents. Local-backend commits remain
on the current machine. Do not run git push for normal MemFS sync; let the
harness push after the turn.
Committed memory changes do not alter the current compiled prompt immediately.
Use /recompile when the current conversation must see changed core memory
right away. Otherwise, the next prompt compilation or conversation will use
the committed revision.
Start With the Harness
Prefer the harness commands over manual API calls, remote construction, or credential-helper edits:
/memfs status # show whether MemFS is enabled and its path
/memfs enable # initialize or repair MemFS setup
/memfs sync # pull the hosted repository
From a shell, the standalone status and pull commands are:
letta memory status --agent "$AGENT_ID"
letta memory pull --agent "$AGENT_ID"
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.
- 4d ago First seen · 180 lines · 42 tokens per session scan A a3884fbd40cc
syncing-memory-filesystem is a skill published in the GitHub repository letta-ai/letta-code (3,178 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 1,608 once invoked, about $0.0002 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.
Other skills, from other repositories
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
kayba-stage-7-fixer
Implement the approved fixes from the action plan and log all changes. Trigger when the user says "run stage 7", "implement fixes", "apply action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md to exist.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
ws-ckpt
工作区快照管理。用户说"保存一下"、"存个快照"时创建 checkpoint，仅限 Linux; 说"回滚"、"撤销"、"恢复到之前"时 rollback;说"删掉快照"时 delete; 说"对比快照"、"快照改了什么"时 diff; 说"看看快照"、"有哪些快照"时 list;说"查看快照状态"、"查看快照剩余空间"时 status。.
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.