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/iamtouchskyer/memex/memex-syncnpx skills add iamtouchskyer/memex --skill memex-syncgit clone --depth 1 https://github.com/iamtouchskyer/memexWrote 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/iamtouchskyer/memex/memex-sync)<a href="https://agentmods.dev/skills/iamtouchskyer/memex/memex-sync"><img src="https://agentmods.dev/badge/skills/iamtouchskyer/memex/memex-sync.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.00015 | $0.00589 |
| Opus 5 | $0.00008 | $0.00295 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
memex-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 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.
What it actually says
Memory Sync
Sync your Zettelkasten cards across devices using git.
Tools Available
memex sync --init <url>— initialize sync with a git remotememex sync --init— auto-create a private GitHub repo viaghCLImemex sync— pull remote changes, commit local changes, pushmemex sync --status— show sync configuration and last sync timememex sync on|off— enable/disable auto-sync after every write/archive
Process
digraph sync {
"User invokes /memex-sync" -> "memex sync --status";
"memex sync --status" -> "Configured?" [shape=diamond];
"Configured?" -> "memex sync" [label="yes"];
"Configured?" -> "Ask user for repo URL" [label="no"];
"Ask user for repo URL" -> "User provides URL?" [shape=diamond];
"User provides URL?" -> "memex sync --init <url>" [label="yes"];
"User provides URL?" -> "memex sync --init (auto-create via gh)" [label="no, use gh"];
"memex sync --init <url>" -> "Report success";
"memex sync --init (auto-create via gh)" -> "Report success";
"memex sync" -> "Report result";
}
Step 1: Check status
Run memex sync --status to see if sync is already configured.
Step 2: Initialize (if needed)
If sync is not configured:
- Ask the user if they have a git repo URL for their cards
- If yes:
memex sync --init <url> - If no:
memex sync --init(auto-creates a privatememex-cardsrepo on GitHub viaghCLI)
Step 3: Sync
If already configured, run memex sync to push and pull changes.
Step 4: Report
Tell the user the result. If sync failed, show the error message.
Rules
- Never force-push —
memex syncusesgit fetch+git mergethengit push - On conflict — report the error and tell the user to resolve manually in
~/.memex - Auto-sync — only suggest
memex sync onif the user asks about it; don't enable by default
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 · 60 lines · 15 tokens per session scan A d70735cdb92c
memex-sync is a skill published in the GitHub repository iamtouchskyer/memex (141 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 589 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.
Other skills, from other repositories
memory-curation
When you have read / processed a workspace asset in this session and learned something durable about it, write a memory page so future sessions benefit. Maintain the workspace wiki's hierarchical structure as it grows.
memory
Persist and retrieve agent memory across sessions — write durable notes, read by path, recall via semantic search, list/delete, and consolidate. Use whenever the user asks to remember/forget something, when you need to look up past decisions or context, or when episodic state matters beyond the current turn. Executes…
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
emulo
Use when the user explicitly asks to run, set up, update, re-mine, or deepen Emulo from real local AI coding-session history and native emulo:mine is not available. This is the cross-agent skills.sh bootstrap, not the native namespaced plugin.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.