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/lolaplex/agents-memory/agents-mdgit clone --depth 1 https://github.com/Lolaplex/agents-memoryWrote 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/lolaplex/agents-memory/agents-md)<a href="https://agentmods.dev/instructions/lolaplex/agents-memory/agents-md"><img src="https://agentmods.dev/badge/instructions/lolaplex/agents-memory/agents-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.01011 | $0.01011 |
| Opus 5 | $0.00505 | $0.00505 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
agents-memory AGENTS.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 3d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent install (this repo)
You are installing local agent memory for the human. Do every step yourself. Do not dump a command list for them to run.
CLAUDE.md at this repo root is a git symlink to this file — edit AGENTS.md only. Sync does not rewrite engine-root CLAUDE.md (installed always-on lives in ~/.agents/). On Windows without symlink privilege the checkout may be a short stub; enable Developer Mode or recreate the symlink from git. Installed always-on: ~/.agents/AGENTS.md; Gemini, Zed, and ~/.claude/ bind to it. Foreign ~/.claude/CLAUDE.md is replaced on sync — back it up first. See abi/PLATFORM.md.
Live store is ~/.agents/memory (user) plus <repo>/.agents/memory (project). Never commit those live files. This clone's examples/*.example.* are scaffolding only. Run python -m agents_memory consolidate if live markdown leaked into memory/ or examples/.
Python is a package: src/agents_memory/. After pip install -e ., use python -m agents_memory (or agents-memory on PATH).
Procedure
- Install with the same interpreter you will keep using:
python -m pip install -e .- Windows:
py -3is fine if that is what your Agent uses. macOS/Linux:python3ifpythonis missing.
- First
python -m agents_memory sync --initcopies examples into~/.agents/memoryif missing, and runsconsolidate_repo_leaks()so nothing live stays in this clone. - Ask the human once (one short question batch):
- name / work
- how agents should talk
- stack defaults
- which folders hold their repos (absolute paths or
~/...) - any monorepo parents whose child repos should also be tracked →
expand_children
- Write
~/.agents/memory/USER.md(real identity, not emptyName:) andscan.json(rootsmust exist on disk).agent_rule_namedefaultuser-rules.mdcis fine. - Run
python -m agents_memory sync --initfrom this repo root.- Copies examples only if live files are missing (never overwrites filled
USER.md). - Writes your Agent always-on inject + canonical
~/.agents/AGENTS.mdwithCLAUDE.mdbound to it (Gemini,~/.claude/AGENTS.md). Does not create.agents/or.cursor/inside this engine clone. - Ensures each registered repo has
.agents/memory/files only (README.md,staging/captured.md) andprojects/<slug>/README.mdas a link. No empty subfolders. No.cursor/in repos (scan skips.cursor). - Merges
agents-memoryinto host MCP config (~/.cursor/mcp.jsonwhen your Agent uses it) using this Python (sys.executable -m agents_memory.mcp_server). Other MCP servers stay. - Merges host MCP servers into Zed
context_serversand mirrors user skills into~/.agents/skills.
- Copies examples only if live files are missing (never overwrites filled
- Run
python -m agents_memory inventory. For each unknown folder: register (slug, path, role, stack) or--ignore. For missing: ask before deleting. - Run
python -m agents_memory ingest catalogto (re)build~/.agents/memory/chats-index.mdfrom local chat stores (Open AI GDPR export, Cursor, VS Code, Antigravity, Pi, …). Titles + paths only. Optional:python -m agents_memory ingest extract(Python filters → staging). Distill with MCPdistill_batch/ skillmemory-distill. - If you edited
USER.md/scan.jsonafter--init, runpython -m agents_memory syncagain. - Tell the human one thing: reload your Agent (MCP). You cannot do that for them.
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.
- 3d ago First seen · 41 lines · 1,011 tokens per session scan A 2d4ed0659c80
agents-memory AGENTS.md is an instructions file published in the GitHub repository Lolaplex/agents-memory (3 stars, last pushed 2d ago), licensed MIT. It adds 1,011 tokens to every session, about $0.0051 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
gortex CLAUDE.md
Claude Code instructions for zzet/gortex, covering gortex, build & test, codebase overview, discovery (read once, then keep using) and llm provider (powers ask and searchsymbols assist: modes).
peon-ping GEMINI.md
Instructions for PeonPing/peon-ping, covering gemini.md - peon-ping, project overview, main technologies, architecture and building and running.
free-ai-gateway AGENTS.md
Instructions for zaber-dev/free-ai-gateway, covering 🤖 free-ai gateway - agentic development guidelines, 🏛️ monorepo architecture & package boundaries, 🛑 strict architectural rules for agents, 💻 essential developer commands and build all packages across monorepo.
codevira CLAUDE.md
Instructions for sachinshelke/codevira, covering codevira — persistent project memory, when to call which codevira tool, at the start of every session, before modifying any file and before adopting a pattern, library, or naming convention.
brain-os AGENTS.md
Instructions for brainOS-HQ/brain-os, covering agents.md, context, the hard rule, tool routing (in order) and mutation safety.
imagine-mcp AGENTS.md
Instructions for n24q02m/imagine-mcp, covering imagine-mcp, architecture, tool signatures, model selection and transport modes.