Borrowing it
Nothing to install: this file belongs to majiayu000/remem. 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/majiayu000/remem/main/AGENTS.mdgit clone --depth 1 https://github.com/majiayu000/rememWrote 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/majiayu000/remem/agents-md)<a href="https://agentmods.dev/instructions/majiayu000/remem/agents-md"><img src="https://agentmods.dev/badge/instructions/majiayu000/remem/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/majiayu000/remem/agents-md"><img src="https://agentmods.dev/badge/instructions/majiayu000/remem/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.01297 | $0.01297 |
| Opus 5.5 | $0.00519 | $0.00519 |
| Sonnet 5.5 | $0.00259 | $0.00259 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
remem 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 1mo 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
remem Agent Instructions
Scope
This file applies to the whole repository unless a nested AGENTS.md overrides it.
remem 的目标是做最强的 Claude Code / Codex 记忆系统，不是最便宜的。所有设计决策优先判断：记忆质量是否提升。成本、延迟、依赖复杂度都排在记忆质量之后。
Start Here
- Run
git status --shortbefore changing files. This repo often has active staged and unstaged work. - Read
README.mdfor user-facing behavior anddocs/ARCHITECTURE.mdfor current runtime/data-flow context. - Read
docs/specs/README.mdbefore treating any olddocs/specs/*.mdfile as pending work. Most historical specs have been implemented, superseded, or absorbed into the current architecture. - For Codex plugin/runtime work, also read
plugins/remem/README.md,plugins/remem/skills/remem/SKILL.md, and the version-sync files listed below. - Use repo-local maintenance skills under
.agents/skills/when a task matches one. - Search existing code and docs before creating new files. Similar-file creation without search is not acceptable.
Core Rules
- Do not remove LLM extraction or automatic capture to save cost. Past zero-LLM direction weakened memory quality.
- Do not rely on agents voluntarily calling
save_memory; automatic hook capture is the primary path, manual save is only a supplement. - No silent degradation for missing or wrong memory/context. User-visible data loss must return an error or log at error level with enough detail to diagnose.
- Prefer current implementation truth over old spec text. When an old spec disagrees with code, verify with tests and update the spec index or spec status instead of reimplementing stale design.
- Keep changes scoped to the requested behavior. Avoid opportunistic refactors unless they are required for correctness.
Spec Routing
Use specs as contracts only after checking their status in docs/specs/README.md.
| Change | Required path |
|---|---|
| Small bugfix with clear root cause | Implement directly, add or update a focused regression test |
| User-facing behavior change | Update README.md and add/update a current spec if behavior is ambiguous |
| Multi-module runtime, DB, hook, or plugin change | Write or update a current docs/specs/<id>/PRODUCT.md and TECH.md pair before implementation |
Historical SPEC-*.md says "proposed" or "active" |
Check docs/specs/README.md and current code first; many are historical implementation references |
| Old refactor-step specs | Treat docs/specs/refactor-steps/ as completed historical split contracts unless current code proves drift |
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.
- 1mo ago Changed · +1 lines · +26 tokens per session da77aa9e3b12
- 1mo ago First seen · 104 lines · 1,271 tokens per session scan A 3b56cff8ff94
remem AGENTS.md is an instructions file published in the GitHub repository majiayu000/remem (34 stars, last pushed yesterday), licensed MIT. It adds 1,297 tokens to every session, about $0.0052 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).
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.