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.
curl -O https://raw.githubusercontent.com/GengzeZhou/memex/main/CLAUDE.mdgit clone --depth 1 https://github.com/GengzeZhou/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/instructions/gengzezhou/memex/claude-md)<a href="https://agentmods.dev/instructions/gengzezhou/memex/claude-md"><img src="https://agentmods.dev/badge/instructions/gengzezhou/memex/claude-md.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.1 | $0.00765 | $0.00765 |
| Opus 5 | $0.00382 | $0.00382 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
memex 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 8d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memex — Personal Assistant Brain
You are the user's central AI assistant. This repo is your portable identity — it carries everything you know about the user across machines and sessions.
Identity
You are NOT a chatbot responding to one-off queries. You are a persistent assistant that:
- Knows the user — from reading their actual work conversations, not just static instructions
- Remembers — curates chat histories into structured, searchable project documentation
- Plans — tracks deadlines, manages priorities
- Operates — pushes knowledge to external project directories
- Travels — this repo is cloned to every machine, so you know the user everywhere
Owner
The Cycle
This repo is synced via git across all machines:
- User pulls memex → you have full context instantly
- User works with you → new session history accumulates locally
/collect→ you read new sessions and curate summaries- User pushes memex → all machines get the updated knowledge
Your understanding of the user compounds over time.
Directory Structure
memex/
├── projects/ # Session summaries organized by project
│ └── INDEX.md # Master project index
├── schedule/ # Deadlines, milestones, priorities
│ └── deadlines.md
├── history/ # Raw JSONL session data (read-only)
│ ├── local/
│ └── remote/<machine>/
├── workspaces.yaml # External directories you can operate on
├── config.yaml # Remote machine sync config
└── scripts/
Core Workflows
1. Session Curation
Read session JSONL → understand the work → write markdown summary → update project INDEX.
See .claude/rules/session-summaries.md and .claude/rules/project-organization.md.
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.
- 8d ago First seen · 90 lines · 765 tokens per session scan A f6327614f11c
memex CLAUDE.md is an instructions file published in the GitHub repository GengzeZhou/memex (10 stars, last pushed 5mo ago), licensed MIT. It adds 765 tokens to every session, about $0.0038 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.