agentmemory is a persistent-memory system that lets AI coding agents retain and search information across sessions. It connects with several coding agents and MCP clients, storing knowledge with confidence scoring, lifecycle handling, knowledge graphs, and hybrid search. The catalogue contains agentmemory integrations such as skills, hooks, commands, a plugin, and an MCP component.
Borrowing it
Nothing to install: this file belongs to rohitg00/agentmemory. 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/rohitg00/agentmemory/main/AGENTS.mdgit clone --depth 1 https://github.com/rohitg00/agentmemoryWrote 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/rohitg00/agentmemory/agents-md)<a href="https://agentmods.dev/instructions/rohitg00/agentmemory/agents-md"><img src="https://agentmods.dev/badge/instructions/rohitg00/agentmemory/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/rohitg00/agentmemory/agents-md"><img src="https://agentmods.dev/badge/instructions/rohitg00/agentmemory/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01875 | $0.01875 |
| Opus 5.5 | $0.00750 | $0.00750 |
| Sonnet 5.5 | $0.00375 | $0.00375 |
| Haiku 4.5 | $0.00187 | $0.00187 |
Grade A, and why
agentmemory 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agentmemory-offline AGENTS.md — 91% identical, 45 lines differ
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentmemory — Agent Instructions
Architecture
agentmemory is a persistent memory system for AI coding agents, built on iii-engine's three primitives (Worker/Function/Trigger). Everything goes through registerFunction/registerTrigger/sdk.trigger() — never bypass iii-engine with standalone SQLite or in-process alternatives.
- Engine: iii-sdk 0.22.1 with @iii-dev/helpers 0.22.1 (WebSocket to iii-engine 0.22.1 on port 49134; the client type is
IIIClient, HTTP requests areHttpRequestfrom@iii-dev/helpers/http) - State: File-based SQLite via iii-engine's StateModule (
./data/state_store.db) - Build: TypeScript → ESM via tsdown, output to
dist/ - Test: vitest (
npm testexcludes integration tests)
Consistency Rules
Before every commit, run npm run docs:sync and commit what it changes. It computes MCP tool counts (all, core, local fallback), REST endpoints, skills, hooks, tests, iii functions, source files, lines of code and KV scopes from the source, and rewrites them in README.md, the translated READMEs, AGENTS.md, INSTALL_FOR_AGENTS.md, plugin manifests, integration READMEs, the stat badges and the src/index.ts banner. The last synced values live in scripts/docs-sync.state.json; commit that file with the rest. npm run docs:check exits non-zero when anything is out of date. When the sync prints check <fact> <old> left in <file>, open that line: either fix it by hand or add its noun to the fact in scripts/docs-sync.ts so the next sync catches it. Never hand-edit these numbers or versions in the docs; change the source and sync.
When adding or removing MCP tools, update:
src/mcp/tools-registry.ts— tool definition +getAllTools()arraysrc/mcp/server.ts— handler case in themcp::tools::callswitchsrc/triggers/api.ts— REST endpoint registrationsrc/index.ts— function registrationtest/mcp-standalone.test.ts— tool count assertion
When adding REST endpoints, update:
src/triggers/api.ts— endpoint registration
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.
- 4d ago Changed · +95 tokens per session d961fa6bdcc7
- 8d ago Changed 57b4000a643f
- 11d ago Changed a5dda280bb4d
- 12d ago Changed e3e58b79222d
- 14d ago Changed 69efea995024
- 15d ago Changed b69da1bc096c
- 18d ago Changed · -10 lines · +121 tokens per session fdcf2e4069e8
- 21d ago Changed · +1 lines · +54 tokens per session 262fe0c82818
- 22d ago Changed f79b1156caac
- 23d ago First seen · 127 lines · 1,605 tokens per session scan A 4870646331b7
agentmemory AGENTS.md is an instructions file published in the GitHub repository rohitg00/agentmemory (29,860 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,875 tokens to every session, about $0.0075 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.