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 skills add aiya000/dotfiles --skill sync-memorygit clone --depth 1 https://github.com/aiya000/dotfilesWrote 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/aiya000/dotfiles/sync-memory)<a href="https://agentmods.dev/skills/aiya000/dotfiles/sync-memory"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-memory/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/skills/aiya000/dotfiles/sync-memory"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-memory.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.00092 | $0.01420 |
| Opus 5.5 | $0.00037 | $0.00568 |
| Sonnet 5.5 | $0.00018 | $0.00284 |
| Haiku 4.5 | $0.00009 | $0.00142 |
Grade A, and why
sync-memory 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 10d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sync-memory
~/.ai-memory/ is a git repository. The local machine and every Claude Code cloud session read
and write the same one, so each side pulls before it reads and pushes after it writes. This
skill is that pull and that push; the skills that write memory call it rather than running git
themselves.
~/.ai-memory/
├── MEMORY-INDEX.md # save-memory's index (merge=union, see below)
├── YYYY-MM-DD-*.md # memory files (save-memory)
└── handoff/
└── <project>-<YYYY-MM-DD-HHMM>.md # handoffs (create-handoff / read-handoff / pop-handoff)
Never write out the real target of ~/.ai-memory -- not in a reply, a commit message, or a
file. Refer to it as ~/.ai-memory/ and to the repository as "the memory repository". The script
never prints it either.
The script is scripts/sync.sh in this skill's directory.
prepare -- before reading or writing
bash <this skill>/scripts/sync.sh prepare
- Local:
~/.ai-memoryis a symlink to a clone; this pulls it. If it is not a symlink, the script stops (exit 3): ask the user to set it up, and do not create it - Cloud session (
CLAUDE_CODE_REMOTE=true), when~/.ai-memorydoes not exist yet:AI_MEMORY_REPOmust be set. If not, stop and tell the user to add it (AI_MEMORY_REPO=<owner>/<name>) to the cloud environment's environment variables- Add the repository to the session with the
add_repotool (claude-code-remote MCP server; load it withToolSearchif it is deferred), then call it with that owner and name andaccess: "push". If it is refused, relay its reason as it is -- the usual one is that the Claude GitHub App is not installed on the memory repository -- and stop - Run
prepare, passing the clone URLadd_reporeturned, if it returned one:sync.sh prepare <url>. It clones into${XDG_CACHE_HOME:-~/.cache}/ai-memoryand points~/.ai-memoryat it. This is the one place a symlink at~/.ai-memoryis created on the user's behalf: a fresh container has nothing to protect, and nothing else can work
prepareis cheap on a second run (it only pulls). Run it once per skill that uses memory
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago Changed · +13 lines feb880b2da89
- 17d ago First seen · 91 lines · 92 tokens per session scan A d189beeec827
sync-memory is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 1,420 once invoked, about $0.0004 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-09-29.
Other skills, from other repositories
restart__pull_request
A pull-request restart workflow for replacing a messy review with a new pull request containing one clean commit and a summary of the earlier discussion.
rescue__pull_request_review
An automated workflow for handling GitHub pull-request review comments, applying requested code changes, committing them, and pushing them back.
submit__pull_request
An automated pull-request submission workflow. A pull request is a request for a code change to be reviewed and merged; this workflow writes its explanation, creates it, watches its automated checks, and fixes failed checks.
write__pull_request
A workflow for writing a pull request description, the explanation attached to a proposed code change for review. It analyses the changes and commit history.
monitor__ci_status
An automated monitor for GitHub Actions, the service that runs checks such as tests after code changes. It watches all checks after a pull request or a push to a pull-request branch and can invoke a failure-recovery process.
monitor__pull_request_conflict
An automated check for GitHub pull requests, which are proposed code changes awaiting review or merging.