memex: Skill for Claude Code

.claude/skills/workspace-sync/SKILL.md

workspace-sync is a skill for Claude Code from GengzeZhou/memex. It costs 34 tokens per session (226 once invoked), scanned A, original, MIT.

A set of procedures for synchronising deadlines and ideas between a memex and external workspaces. A memex is a personal store of notes and connected ideas.

In plain words
What is it for?
Use it to merge deadline changes in both directions or move a session idea into an external workspace as a linked Markdown file.
Why use it?
It reduces duplicated or outdated planning files when information exists in more than one workspace.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is GengzeZhou/memex's own configuration. It tells Claude Code how to work on memex 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 memex configures →

Reuse

Borrowing it

Nothing to install: this file belongs to GengzeZhou/memex. 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/GengzeZhou/memex/main/.claude/skills/workspace-sync/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/GengzeZhou/memex

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 workspace-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/gengzezhou/memex/workspace-sync.svg)](https://agentmods.dev/skills/gengzezhou/memex/workspace-sync)
Your own site
<a href="https://agentmods.dev/skills/gengzezhou/memex/workspace-sync"><img src="https://agentmods.dev/badge/skills/gengzezhou/memex/workspace-sync.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 226 The whole file, excluding the scripts and references it only reads on demand.
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.00034 $0.00226
Opus 5 $0.00017 $0.00113
Sonnet 5 $0.00007 $0.00045
Haiku 4.5 $0.00003 $0.00023

Measured 7d ago against content hash 169652bcda96, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

workspace-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 7d 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/skills/workspace-sync/SKILL.md · 32 lines

What it actually says

Workspace Sync Workflow

Reference @../../workspaces.yaml for workspace definitions.

Sync Operations

Deadlines sync (bidirectional):

  1. Read schedule/deadlines.md in memex
  2. Read the corresponding deadlines file in the target workspace
  3. Merge: take the more recent version of each entry, add new entries from either side
  4. Write the merged result to both locations

Idea migration (memex → workspace):

  1. When a session summary contains an idea worth developing
  2. Extract the idea into a standalone markdown file
  3. Write to the workspace's ideas directory
  4. Link back to the original session summary

Rules

  • Never delete files in external workspaces
  • Always check workspace write permissions before writing
  • Log all sync operations
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. 7d ago First seen · 32 lines · 34 tokens per session scan A 169652bcda96

Subscribe to this mod's changes

workspace-sync is a skill published in the GitHub repository GengzeZhou/memex (10 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 226 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-31.