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 instructions/memi-design/memi/claude-mdgit clone --depth 1 https://github.com/memi-design/memiWrote 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/memi-design/memi/claude-md)<a href="https://agentmods.dev/instructions/memi-design/memi/claude-md"><img src="https://agentmods.dev/badge/instructions/memi-design/memi/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 | $0.02576 | $0.02576 |
| Opus 5 | $0.01288 | $0.01288 |
| Sonnet 5 | $0.00515 | $0.00515 |
| Haiku 4.5 | $0.00258 | $0.00258 |
Grade A, and why
memi 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 5d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mémoire — Guidelines for Claude
Prime Directives
- Operate as an autonomous superagent — read designs, drive canvas, generate specs and code without waiting for permission. Burn tokens for quality. (Why: Mémoire is built for hands-free operation; hesitation breaks the flow.)
- Use Atomic Design exclusively — every component specifies a level: atom → molecule → organism → template → page. (Why: enforced in specs, codegen, and Figma structure.)
- Self-heal after every canvas operation — CREATE → SCREENSHOT → ANALYZE → FIX → VERIFY (max 3 rounds). (Why: floating elements, wrong sizing, and raw hex values are the top defects.)
- Check Code Connect before creating anything —
get_code_connect_mapfirst. Use mapped components when they exist. (Why: duplicate components are the #1 design system debt source.) - Load relevant skills before acting — skills in
skills/define how agents operate. Read the skill file that matches your task.
What is Mémoire
AI-native design intelligence engine. Bridges Figma, user research, and code generation into a spec-driven system. Auto-discovers and connects to the Figma plugin, generates shadcn/ui components from structured specs, and exposes on-canvas agent status widgets for task visibility.
Widget V2 Operating Model
- Use the Figma Control Plane as an operator surface, not only as a bridge transport
- Check
Jobsfirst for sync, capture, inspect, and healer state - Use
Selectionfor node IDs, styles, variants, layout facts, and quick actions - Use
Systemfor bridge state, ports, latency, and buffered change-stream visibility - Treat canvas agent widgets as task/status surfaces, not as a durable communication log
- Use
memi connect --jsonandmemi doctor --jsonwhen an agent needs machine-readable widget and bridge health
Architecture
| Directory | Purpose |
|---|---|
src/engine/ |
Core orchestrator, project detection, registry, token-differ, sync, code-watcher, pipeline |
src/figma/ |
Figma bridge (WebSocket auto-discovery on ports 9223-9232), tokens, stickies |
src/research/ |
Research engine (Excel, web, stickies → insights) |
src/specs/ |
Spec types (component, page, dataviz, design, ia) + Zod validation |
src/codegen/ |
Code generation (shadcn mapper, dataviz, pages) → atomic folders |
src/notes/ |
Mémoire Notes — downloadable skill packs (loader, resolver, installer) |
src/preview/ |
Localhost preview gallery (HTML + API server + pipeline/sync/agent dashboards) |
src/agents/ |
Agent orchestrator, multi-agent registry, task queue, agent bridge, agent workers |
src/mcp/ |
MCP server (stdio transport) — 14 tools, 3 resources for Claude Code/Cursor |
src/tui/ |
Terminal UI (Ink/React) |
src/commands/ |
CLI commands (Commander.js) |
skills/ |
Built-in skill definitions — ship with the npm package |
plugin/ |
Figma plugin (auto-discovers Mémoire on ports 9223-9232) |
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.
- 5d ago First seen · 154 lines · 2,576 tokens per session scan A 8509cf090f21
memi CLAUDE.md is an instructions file published in the GitHub repository memi-design/memi (40 stars, last pushed 2d ago), licensed MIT. It adds 2,576 tokens to every session, about $0.0129 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
python-sdk AGENTS.md
AGENTS.md instructions for modelcontextprotocol/python-sdk, covering development guidelines, note for ai agents, branching model, package management and code quality.
frontmcp AGENTS.md
AGENTS.md instructions for agentfront/frontmcp, a project described as: TypeScript-first framework for the Model Context Protocol (MCP). You write clean, typed code; FrontMCP handles the protocol, transport, DI, session/auth, and execution flow.
brain-in-the-fish CLAUDE.md
Instructions for fabio-rovai/brain-in-the-fish, covering brain in the fish, relationship to open-ontologies, module overview, pipeline and mcp tools.
Web-Algebra CLAUDE.md
Instructions for AtomGraph/Web-Algebra, covering claude.md, project overview, core architecture, key components and commands.
quarry CLAUDE.md
Claude Code instructions for punt-labs/quarry, covering quarry, mandatory reading, architecture, how a query works and how ingestion works.
cdc-health-mcp-server CLAUDE.md
Instructions for cyanheads/cdc-health-mcp-server, covering agent protocol, domain, api surface, socrata api endpoints and cdc wonder api.