What is pce-memory CLAUDE.md?

Project instructions for pce-memory, an MCP server in a JavaScript and TypeScript monorepo. A monorepo is one repository containing several related applications and packages.

Develop the pce-memory server, build and test the monorepo, run type checks and linting, format code, and run its TLA+ and Alloy formal-verification checks.

It gives contributors the commands and project map needed to install dependencies, build all packages, run tests, and check code consistently.

pce-memory CLAUDE.md — Instructions file by CAPHTECH

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/caphtech/pce-memory/claude-md

Clone the repo

git clone --depth 1 https://github.com/CAPHTECH/pce-memory

Per session 1,689 This file is loaded in full into every session.

When invoked 1,689 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.

Model	Per session	Once invoked
Fable 5	$0.01689	$0.01689
Opus 5	$0.00844	$0.00844
Sonnet 5	$0.00338	$0.00338
Haiku 4.5	$0.00169	$0.00169

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

Security

Grade A, and why

pce-memory CLAUDE.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.

CLAUDE.md · 223 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Build & Development Commands

# Install dependencies (monorepo)
pnpm install

# Build all packages
pnpm build

# Run all tests
pnpm test

# Run single test file
pnpm test apps/pce-memory/test/specific.test.ts

# Property-based tests only
pnpm test:pbt

# Type checking
pnpm typecheck

# Linting
pnpm lint
pnpm lint:fix

# Formatting
pnpm format
pnpm format:check

# Formal verification (TLA+/Alloy)
pnpm formal:tla
pnpm formal:alloy

pce-memory (MCP Server) specific

cd apps/pce-memory

# Development mode
pnpm dev

# Build
pnpm build

# Run tests
pnpm test

# Type check
pnpm typecheck

Architecture Overview

Monorepo Structure

apps/pce-memory - MCP server (main package, published to npm as pce-memory)
packages/pce-boundary - Boundary validation & redaction
packages/pce-embeddings - Embedding provider abstraction (OpenAI/Local)
packages/pce-policy-schemas - YAML policy schemas
packages/pce-sdk-ts - TypeScript client SDK

pce-memory Internal Architecture

src/
├── index.ts          # MCP server entry (stdio transport)
├── core/handlers.ts  # Tool handlers (central dispatcher)
├── domain/           # State machine, errors, validation
├── store/            # DuckDB persistence (claims, entities, relations, etc.)
├── state/            # Runtime state (memoryState, layerScopeState)
├── daemon/           # Standalone daemon process
└── client/           # Proxy client (auto-starts daemon)

State Machine Flow

Uninitialized → PolicyApplied → HasClaims → Ready
                     │              │          │
                     └──────────────┴──────────┘ (循環可能)

policy_apply - Initialize with policy (Uninitialized → PolicyApplied)
upsert - Register claims (PolicyApplied/HasClaims/Ready → HasClaims)
activate - Build active context (HasClaims/Ready → Ready)
feedback - Update critic scores (Ready state only)

Read the full file on GitHub · 223 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.

2d ago First seen · 223 lines · 1,689 tokens per session scan A 871af65efc3c

Subscribe to this mod's changes

pce-memory CLAUDE.md is an instructions file published in the GitHub repository CAPHTECH/pce-memory (3 stars, last pushed 5mo ago), licensed MIT. It adds 1,689 tokens to every session, about $0.0084 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-31.

Languages Memory and context Testing

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

pce-memory CLAUDE.md