agentmods.dev

amem: Instructions file for Codex

AGENTS.md

amem AGENTS.md is an instructions file for Codex, OpenCode from fuyucn/amem. It costs 458 tokens per session, scanned A, original, MIT.

Repository instructions for working on the fuyucn/amem project, including how to use its persistent memory system. Persistent memory stores project knowledge outside the current chat.

In plain words
What is it for?
Use it when starting, continuing, or ending substantial work on amem so relevant memory is recalled and durable updates are recorded.
Why use it?
It keeps important project decisions, procedures, and lessons available across working sessions.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is fuyucn/amem's own configuration. It tells Codex and OpenCode how to work on amem 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 amem configures →

not rated 0repo 2mo ago A scan 458 tokens original MIT
View source ↗ fuyucn/amem
Reuse

Borrowing it

Nothing to install: this file belongs to fuyucn/amem. 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/fuyucn/amem/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/fuyucn/amem

Made for: 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 amem AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/fuyucn/amem/agents-md"><img src="https://agentmods.dev/badge/instructions/fuyucn/amem/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 458 This file is loaded in full into every session.
When invoked 458 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.00458 $0.00458
Opus 5.5 $0.00183 $0.00183
Sonnet 5.5 $0.00092 $0.00092
Haiku 4.5 $0.00046 $0.00046

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

Security

Grade A, and why

amem 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 2mo 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 · 43 lines

What it actually says

Amem project agent instructions

Persistent memory (required)

This repo’s long-term memory lives in Amem (local SQLite knowledge graph), not in chat history.

When the amem MCP server is available, you MUST:

Start of a working session

  1. Call working_memory (no args or today’s date).
  2. Call recall with a short query for the active task/project (e.g. current feature name).
  3. Ground your plan on returned units; cite unit titles when relevant.

While working

  • After any durable decision, plan, procedure, or lesson: save_unit with the right type.
  • Prefer atomic units (one idea each). Use tags like project slug / area.
  • If the user pastes a long transcript or meeting notes: ingest with extract=true.

Before ending a substantial session

  • ingest a short session summary (what changed, open questions, next steps).
  • Optionally curate with preset fast if many new units were added.

Do not

  • Re-state large known project facts from scratch if recall already returned them.
  • Store secrets (API keys, tokens, passwords) into Amem.

UI visibility

Humans watch http://127.0.0.1:8321 → Activity for new writes and recalls. Prefer clear unit titles so the feed is readable.

Closed-loop Amem usage (mandatory on this machine)

User requirement: Amem is only valuable if this agent uses it while working.

Every non-trivial turn:

  1. node tools/amem-loop.mjs start "<task keywords>" (or REST equivalent working_memory+recall)
  2. Do the work grounded on recalled units
  3. node tools/amem-loop.mjs save decision|procedure|lesson|preference "<title>" "<body>" for durable outcomes
  4. node tools/amem-loop.mjs end "<milestone summary>" and/or rely on Stop hook
  5. Confirm Activity/Graph feedback before claiming completion

Shared endpoint: http://127.0.0.1:8321 DB: data/amem.db

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. 2mo ago First seen · 43 lines · 458 tokens per session scan A aef73d332da2

Subscribe to this mod's changes

amem AGENTS.md is an instructions file published in the GitHub repository fuyucn/amem (0 stars, last pushed 2mo ago), licensed MIT. It adds 458 tokens to every session, about $0.0018 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-31.

Memory and context
Related

amem AGENTS.md compared with instructions from other repositories

amem AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
amem AGENTS.mdfuyucn/amemInstructions file02mo agoMITA458Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode