memory-service: Instructions file for Codex

AGENTS.md

memory-service AGENTS.md is an instructions file for Codex, OpenCode from chirino/memory-service. It costs 913 tokens per session, scanned A, original, Apache-2.0.

Project instructions for a memory service that stores conversations between users and language models. The service supports replaying and branching conversations.

In plain words
What is it for?
Use them when changing the memory service, especially its conversation, agent API, and project-knowledge features.
Why use it?
They give AI assistants the project’s key concepts, development guidance, and notes so they can work consistently without rediscovering them.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 memory-service AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/chirino/memory-service/agents-md"><img src="https://agentmods.dev/badge/instructions/chirino/memory-service/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 913 This file is loaded in full into every session.
When invoked 913 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.00913 $0.00913
Opus 5.5 $0.00365 $0.00365
Sonnet 5.5 $0.00183 $0.00183
Haiku 4.5 $0.00091 $0.00091

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

Security

Grade A, and why

memory-service 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.

AGENTS.md · 39 lines

How it starts

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

Memory Service

A memory service for AI agents that stores messages exchanged with LLMs and users, supporting conversation replay and forking.

Recording knowledge

Record something only if it caused a real failure or wasted significant time, and a future session couldn't learn it from the code, tests, contracts (contracts/), or site docs. Most discoveries don't qualify. When one does, use the first destination that fits:

  1. Test: an invariant a test can enforce, including site doc tests for what the docs must say.
  2. Code comment at the code the gotcha is about. Keep it short.
  3. Skill (.skills/<name>/SKILL.md): a multi-step procedure. Its description must name the files or tasks that should trigger it.
  4. This file: only a cross-cutting trap that most sessions need and that has no code location. One or two lines.

Don't copy contract details (endpoints, enum values, field semantics) into prose; point to the contract. Don't record what a file contains, what changed, or future plans. If you find a record here, in a skill, or in a comment that's wrong, fix or delete it in the same change. If a skill loaded but wasn't relevant, tighten its description.

Key concepts

  • Agent apps sit between end users and the memory service and mediate all operations. The Agent API serves them, and some of its operations are safe to expose to frontends such as SPAs. The Admin API is for administration.
  • contracts/ holds the OpenAPI (contracts/openapi/) and protobuf (contracts/protobuf/) sources of truth.
  • Local developer tooling (compose.yaml, task dev*, embedded MCP) favors zero-configuration ease of use over production hardening. Keep demo credentials and don't add mandatory secret-generation steps.

Commands

  • task dev:memory-service runs the Go service with Air hot reload on port 8082 and starts its dependencies with Docker Compose.
  • The Maven wrapper and reactor root are under java/. From the repo root, run ./java/mvnw -f java/pom.xml ....
  • Verify each change with the checks for the modules you touched. The build-test skill lists them.

Read the full file on GitHub · 39 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. 1mo ago Changed · -109 lines · -4,544 tokens per session e9fde1d577bc
  2. 1mo ago Changed · +1 lines · +89 tokens per session 2be079571a00
  3. 1mo ago Changed e8fe4d6bf6b5
  4. 1mo ago Changed · +2 lines · +123 tokens per session 1cad59b114a1
  5. 1mo ago Changed · +3 tokens per session 1e282f0017c5
  6. 1mo ago Changed · +1 lines · +105 tokens per session f0af284374ac
  7. 1mo ago Changed · +132 tokens per session 55906835355d
  8. 2mo ago First seen · 144 lines · 5,005 tokens per session scan A 6c0689500370

Subscribe to this mod's changes

memory-service AGENTS.md is an instructions file published in the GitHub repository chirino/memory-service (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 913 tokens to every session, about $0.0037 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,715 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,461 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,750 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