khms-memory AGENTS.md

Repository instructions for setting up and using KHMS Memory, a system that stores approved knowledge cards for future coding sessions. It defines where memory lives, how notes are proposed, and how approved cards remain immutable.

In plain words
What is it for?
Use them to configure the memory directory, capture notes during work, propose and approve knowledge cards, supersede incorrect cards with new ones, and verify the installation.
Why use it?
They prevent unreviewed or fabricated information from becoming trusted memory. They also preserve old approved cards as evidence instead of silently changing them.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/kostey/khms-memory/agents-md
Clone the repo
git clone --depth 1 https://github.com/kostey/khms-memory

Made for: Codex, OpenCode.

Per session 3,595 This file is loaded in full into every session.
When invoked 3,595 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.03595 $0.03595
Opus 5 $0.01798 $0.01798
Sonnet 5 $0.00719 $0.00719
Haiku 4.5 $0.00360 $0.00360

Measured 2d ago against content hash 26fd6cc51579, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

khms-memory 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 2d 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 · 247 lines

How it starts

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

AGENTS.md — set up KHMS memory for yourself, in one pass

You are an agent that has been told: "set up your memory per this repo." This file is the whole job. Work top to bottom. Everything you need is in this repository; nothing here needs network access, a database, or a service.

Before you start, know the two rules that outrank convenience:

  1. You may not write into memory/know/ without your operator's approval. Background stages propose; approval is a separate, human-or-strong-model step. This is what keeps a fabricated card from becoming a remembered fact.
  2. Cards are immutable once approved. You will be tempted to "just fix" one. Don't. Write a new card that supersedes it. The wrong old card is evidence about how you were wrong.

Step 1 — Decide where memory lives, and set KHMS_ROOT

Pick a directory outside the code you work on — memory outlives any one project. Everything below is relative to it. Every script in tools/ reads the environment variable KHMS_ROOT and falls back to its own parent directory, so a copied tools/ directory works with no edits.

export KHMS_ROOT="$HOME/.agent-memory"      # put this in your shell profile too

Create the layout and copy the tooling:

git clone <this-repo> /tmp/khms && /tmp/khms/tools/khms_init.sh "$KHMS_ROOT"

khms_init.sh is idempotent: it creates the directories, the ID counter, an empty tag registry, and copies tools/ and tools/prompts/ into $KHMS_ROOT. It writes nothing into memory/know/.

Resulting layout — memorize it, you will refer to it constantly:

$KHMS_ROOT/
  MEMORY.md                 generated index; keep this in your context always (≤80 lines)
  memory/know/K-*.md        the cards — one claim per file, immutable
  memory/views/             generated: topics/<tag>.md, by-type/<type>.md, tags.md, recent.md
  memory/inbox/             proposals awaiting review (temp labels, no IDs yet)
  memory/inbox/.staging/    what each pipeline stage was actually handed (forensics)
  memory/archive/know/      superseded and condensed cards — "fog", still greppable
  journal/YYYY-MM-DD.md     what happened today, written as it happens
  tools/                    the scripts below; tools/.next_id is the ID counter

Read the full file on GitHub · 247 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. 2d ago First seen · 247 lines · 3,595 tokens per session scan A 26fd6cc51579

Subscribe to this mod's changes

khms-memory AGENTS.md is an instructions file published in the GitHub repository kostey/khms-memory (11 stars, last pushed 3d ago), licensed MIT. It adds 3,595 tokens to every session, about $0.0180 per session on Opus 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

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

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 · 6,785 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 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,345 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js 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,296 tokens