emem: Instructions file for Claude Code

AGENTS.md

emem AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from Vortx-AI/emem. It costs 2,595 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for coding agents working on emem, a service that answers questions, finds stored information, and returns signed receipts that can be checked later.

In plain words
What is it for?
Use them when developing emem or calling its question, location, recall, verification, and agent-integration interfaces.
Why use it?
They explain how to use the service, understand the codebase, and follow its build, testing, debugging, and safety rules.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: Claude Code plugin machinery, but also the file is AGENTS.md. Also seen: mentions Claude Code; mentions AGENTS.md; mentions Codex.

This is Vortx-AI/emem's own configuration. It tells Claude Code, Codex and OpenCode how to work on emem itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything emem configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/ubuntu/emem-ops/pending_deploy.sh.

Reuse

Borrowing it

Nothing to install: this file belongs to Vortx-AI/emem. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Vortx-AI/emem/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Vortx-AI/emem

Made for: Claude Code, Codex, OpenCode.

Wrote 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.

agentmods badge for emem AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/vortx-ai/emem/agents-md/github.svg)](https://agentmods.dev/instructions/vortx-ai/emem/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/vortx-ai/emem/agents-md"><img src="https://agentmods.dev/badge/instructions/vortx-ai/emem/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.

agentmods 80×15 button for emem AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/vortx-ai/emem/agents-md"><img src="https://agentmods.dev/badge/instructions/vortx-ai/emem/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,595 This file is loaded in full into every session.
When invoked 2,595 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02595 $0.02595
Opus 5.5 $0.01038 $0.01038
Sonnet 5.5 $0.00519 $0.00519
Haiku 4.5 $0.00260 $0.00260

Measured 4d ago against content hash b230b794155c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

emem 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.

AGENTS.md · 189 lines

How it starts

The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This file is the README for coding agents working on the emem source. Per the agents.md convention (OpenAI Codex, 2025; Linux Foundation AAIF, Dec 2025): build commands, test rules, code style, and what's off-limits during autonomous runs. End users of the protocol should read docs/agents.md and skills.md instead; those describe how to use emem from an agent.

First 5 minutes (using emem as an agent)

If you only want to call emem (not edit its source), here is zero to a signed answer in three calls:

  1. Ask. POST /v1/ask {"question":"what is the NDVI near Mount Fuji?"} (MCP tool emem_ask, or emem_intent / POST /v1/intent for a structured single-shot). The classifier routes the question to one of four paths: a self-description of emem, a corpus audit (a redirect to the coverage endpoints, with no receipt), a hunter sweep over a region, or a point answer. The hunter sweep and the point answer carry a signed receipt. Ask answers point questions with a current value, so send a change question ("how has X changed") to emem_intent with did_change, or to emem_diff. This is the fastest path.
  2. Or take control. POST /v1/locate {"place":"Mount Fuji"} → a cell64, then POST /v1/recall {"cell":"<cell64>"} (auto-materialises on a miss).
  3. Cite it. Verify the receipt offline at /verify or via POST /v1/verify_receipt; hand other agents an emem:fact: token from emem_memory_token (or emem_memory_bundle for several).

Newer "connect & evolve" surfaces (typed temporal edges, the contradiction-fed refinement loop) are walked end-to-end in examples/connect-and-evolve.md. Full usage guide: docs/agents.md. The rest of this file is for agents editing the source.

Repo shape

Rust workspace, 19 crates, version 2.4.4, MSRV 1.91. emem-guard is the verdict server for AI inference checkpoints (Anthropic Inference hooks, Claude Code hooks); it is a separate binary and shares no code path with the responder. The bulk of the code lives in crates/emem-api-rest/src/lib.rs (HTTP/MCP router plus every inline materializer) and crates/emem-fetch/src/*.rs (27 data connectors + 8 utility modules). Earlier versions ran Clay, Prithvi, Galileo and JEPA-v2 on a GPU sidecar; facts they signed still verify. Web surface in web/ is plain HTML, no build step, included via include_str!.

Read the full file on GitHub · 189 lines

Changes

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.

  1. 4d ago Changed b230b794155c
  2. 6d ago Changed · +14 lines · +208 tokens per session scan B → A 22bc23fa26b7
  3. 12d ago Changed 6aaa4eb8a128
  4. 13d ago Changed 5359f8e953a7
  5. 23d ago Changed · +5 lines · +94 tokens per session c9463442c989
  6. 24d ago Changed bddf2ff26150
  7. 28d ago Changed · -3 lines · -62 tokens per session f7b9064f81d1
  8. 29d ago Changed 31566b5a1c11
  9. 1mo ago Changed · +17 tokens per session 9c7f249e9f2d
  10. 1mo ago First seen · 173 lines · 2,338 tokens per session scan B c1de2dcd81ce

Subscribe to this mod's changes

emem AGENTS.md is an instructions file published in the GitHub repository Vortx-AI/emem (72 stars, last pushed 3d ago), licensed Apache-2.0. It adds 2,595 tokens to every session, about $0.0104 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.

Related

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,549 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens