Borrowing it
Nothing to install: this file belongs to camgitt/memoir. 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/camgitt/memoir/main/CLAUDE.mdgit clone --depth 1 https://github.com/camgitt/memoirWrote 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/camgitt/memoir/claude-md)<a href="https://agentmods.dev/instructions/camgitt/memoir/claude-md"><img src="https://agentmods.dev/badge/instructions/camgitt/memoir/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.00719 | $0.00719 |
| Opus 5 | $0.00360 | $0.00360 |
| Sonnet 5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
memoir 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 6d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
memoir — Persistent Memory for AI Coding Tools
Project
- Package: memoir-cli (npm), v3.12.0 (see package.json — this line goes stale)
- Website: memoir.sh (static HTML on Vercel)
- Repo: https://github.com/camgitt/memoir
- License: MIT
- Stack: Node.js CLI + Supabase (auth, storage, PostgreSQL)
What it does
CLI + MCP server that gives AI tools persistent memory. Your AI can search, read, and save memories across sessions, tools, and machines. Supports 11 tools: Claude Code, Cursor, Windsurf, Gemini, Copilot, Codex, ChatGPT, Aider, Zed, Cline, Continue.dev.
Architecture
- CLI commands: push, restore, snapshot, resume, migrate, diff, profile, doctor, share, upgrade, consolidate, login (--signup), forgot-password, recall, forget, validate, why, note/goal/next/done/ask
- MCP server: 15 tools — memory: memoir_remember (aliases/tags → frontmatter), memoir_recall (passages, field-weighted, cached — src/memory/search.js), memoir_read, memoir_list, memoir_profiles, memoir_status, memoir_consolidate; session continuity: memoir_set_goal, memoir_add_next, memoir_complete_next, memoir_note, memoir_ask, memoir_session, memoir_why, memoir_forget (absolute tombstone, --purge redacts)
- Session continuity: AI records goals/next-actions/decisions into session.json, auto-rendered into CLAUDE.md so the next session picks up where the last ended
- Consolidate: scans all tool memories for duplicates, stale files, and bloat (
--smartadds a Gemini Flash semantic pass) - Cloud sync: Supabase auth (email/password), gzipped bundles in Storage, PostgreSQL metadata
- Encryption: AES-256-GCM, async scrypt, client-side before upload (zero-knowledge)
- Tiers: Free (10 cloud backups), Pro ($15/mo, 100 backups + version history — purchasable via
memoir upgrade, Stripe checkout wired), Teams ($29/seat, planned)
Key files
bin/memoir.js— CLI entry pointsrc/— core logic (sync, auth, encryption, mcp server)GAMEPLAN.md— business plan and roadmap
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.
- 6d ago First seen · 43 lines · 719 tokens per session scan A 0c74d88e03c1
memoir CLAUDE.md is an instructions file published in the GitHub repository camgitt/memoir (14 stars, last pushed today), licensed MIT. It adds 719 tokens to every session, about $0.0036 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 instructions, from other repositories
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.
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).
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).
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.
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.