The memory plane for Codex.

A bounded, fail-closed project-memory system for Codex CLI. Optional Claude Code support on the same skill source.

English · 中文

An agent should remember a project the way a careful engineer does: a short brief, a map, a list of traps — not a diary that never ends.

Codex already writes code, reviews diffs, and triages failures. What it still lacks, out of the box, is a durable, size-capped, attributed memory of the repo that the next session can trust. This pack is that layer: skills, a constitution, an installer Codex can run unaided, and a verifier that fails closed.

Clone, then tell Codex:

Read INSTALL.md in this pack and follow it to install the memory system on this machine.

No GUI. The installer is a program for the agent. Installs are reversible. No wiki? Only the project-memory skill is enabled.

Codex is strongest when the repo already knows how it wants to be maintained. This pack is that contract, written so an agent can install, obey, and prove it.

It is first-class Codex infrastructure: AGENTS.md sections, Codex skills, an agent-executable INSTALL.md, and VERIFY.md as acceptance — the same shape as a serious maintainer toolchain, not a prompt pack you paste once and forget.

Agents either forget the project between sessions, or they “remember” by appending to handoff notes and changelogs. Those files have no ceiling. The next session burns tens — sometimes hundreds — of thousands of tokens on yesterday’s residue before any real work starts.

That is not memory. It is context pollution with a git history.

• A constitution, not a vibe. SYSTEM.md is the spec: tiers, byte budgets, attribution, replace-guards, “do not write secrets.” Skills do not outrank it.
• An agent-native installer. INSTALL.md is for Codex to execute: adapt paths, merge global rules, enable repos, write a machine receipt, roll back.
• A verifier, not a checklist. VERIFY.md is assertions with real exit codes. Pack bytes are pinned by SHA256SUMS.
• One skill source, two harnesses. Codex holds the files; a second harness gets symlinks. No forked copies.
• Fail-closed upgrades. Fresh / upgrade / migrate are different contracts. Older packs are sealed first.
• Secret-hygiene as a boundary. The optional coach path sanitizes learning records before they can reach a central wiki. The regression suite exists because this was treated as a security gate.

Four layers. Each has one job.

flowchart TB
  subgraph pack [This pack]
    I[INSTALL.md]
    S[SYSTEM.md]
    V[VERIFY.md]
    SK[skills/]
  end
  subgraph machine [Target machine]
    H1[Primary harness skills]
    H2[Secondary harness symlinks]
    G[Harness global rules]
    T[Machine facts]
  end
  subgraph repos [Each repository]
    D[docs/ai bounded pack]
  end
  I --> H1
  H1 --> H2
  I --> G
  I --> T
  I --> D
  S -.-> SK
  V -.-> H1
  V -.-> D

Handoff is a single snapshot under a replace-guard (flock on an absolute lock path). It is not a log.

This is the part a maintainer cannot fake with a prettier README.

• Secrets never enter memory files. The constitution forbids it. Shape-based sanitizers are a backstop, not the policy.
• Upgrades cannot silently clobber your edits. The install receipt is a hash table. Mismatches are reported and kept.
• Acceptance is executable. VERIFY.md fails closed. tests/ exists so closed review findings cannot regress.
• Integrity is pinned. sha256sum -c SHA256SUMS is the first install gate.
• Attribution is mandatory. Every memory write carries a stable harness/model actor. History is not rewritten to flatter the present.

Enforced in spec and in the verifier:

1. Governance must cost less than the mess it prevents. No mechanism without a reproduced failure.
2. Closed failures become assertions. A finding that is not executable will come back.
3. Archive, do not destroy. Over-budget files go to history/. Migrations seal first.
4. Writers do not store secret values. Sanitizers are the second line.

git clone https://github.com/tudoumashu/ai-memory-skillpack.git
cd ai-memory-skillpack
sha256sum -c SHA256SUMS

Requirements: Linux or WSL, bash ≥ 4.4, git, rg, sha256sum. Python ≥ 3.10 only for project-mastery-coach. macOS needs GNU sha256sum / flock / readlink -f and a newer bash, or the installer stops.

Then tell Codex:

Read INSTALL.md in this pack and follow it to install the memory system on this machine.

Adapter table, receipt schema, rollback: INSTALL.md. Acceptance: VERIFY.md.

No Obsidian vault? The installer skips llm-wiki and project-mastery-coach and installs only ai-project-memory. Wiki lint/query scripts are not in this repo.

Shipped skills contain example absolute paths and actor strings. Those are adapter source values, not a requirement to use those directories or models.

If a skill text conflicts with SYSTEM.md, the constitution plus the machine’s adapter values win.

What you can verify in this repository without trusting a pitch:

• Tagged releases through v1.25.1; pack identity v1.25
• Agent-executable installer, constitution, and post-install verifier checked in as first-class files
• Coach-script regression suite under tests/
• MIT license, public source, no telemetry in the pack

sha256sum -c SHA256SUMS
bash tests/run.sh python3 skills/project-mastery-coach/scripts/project_mastery_state.py

Change a listed file → regenerate SHA256SUMS, or the installer integrity gate fails.

MIT