What is zaxy AGENTS.md?

Project instructions for Zaxy, a memory system for groups of AI agents. It stores an append-only event log, rebuilds a graph of relationships from that log, and returns cited memory results.

Use them when developing, operating, or debugging Zaxy's memory storage, graph projections, replay process, locks, and backends.

They explain which data is permanent, which data can be rebuilt, and how concurrent access must be controlled. This helps prevent corruption or treating temporary derived data as the source of truth.

How syndicalt/zaxy configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to syndicalt/zaxy. 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/syndicalt/zaxy/master/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/syndicalt/zaxy

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/syndicalt/zaxy/agents-md/github.svg)](https://agentmods.dev/instructions/syndicalt/zaxy/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/syndicalt/zaxy/agents-md"><img src="https://agentmods.dev/badge/instructions/syndicalt/zaxy/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/syndicalt/zaxy/agents-md"><img src="https://agentmods.dev/badge/instructions/syndicalt/zaxy/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Model	Per session	Once invoked
Fable 5.1	$0.01417	$0.01417
Opus 5.5	$0.00567	$0.00567
Sonnet 5.5	$0.00283	$0.00283
Haiku 4.5	$0.00142	$0.00142

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

Security

Grade A, and why

zaxy 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 · 101 lines

How it starts

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

AGENTS.md — working on Zaxy

Zaxy is an event-sourced memory runtime for agent fleets: an append-only, hash-chained JSONL log (Eventloom) is the source of truth; an embedded LadybugDB graph projection and every cache are replayable derivatives; recall is a cited Memory Checkout. Published to PyPI as zaxy-memory (CLI binary zaxy; the bare zaxy name on PyPI is an unrelated package). Docs site: https://zaxy.io.

Controlling docs: CLAUDE.md (operating manual: conventions, named failure modes, quality bars, escalation rules) + docs/architecture.md + README.md. This file is the condensed cross-tool orientation; when it and the code disagree, the code wins — fix this file.

Architecture in five invariants

.eventloom/*.jsonl is append-only truth. Never edit, truncate, or delete it. Everything under .eventloom/projections/ is derived and rebuildable — move it aside (never rm) and replay rebuilds it.
Embedded LadybugDB is the default backend: file-based, in-process, zero-daemon. Neo4j is an optional sidecar; pgGraph and LatticeDB are experimental. Nothing may assume Neo4j is primary.
One owner per store (exclusive write lock); concurrent owners corrupt the WAL. Owner locking, reaping, self-heal, and the pre-open bloat guard live in the embedded runtime — see docs/runbook.md.
MCP is the primary interface (memory_checkout is the front door); the CLI is the human/debug surface. The MCP tool contract is snapshot-pinned in docs/examples/mcp-tool-contract.json — changing a tool means regenerating the snapshot in the same PR.
Recall is cited or it doesn't count: current facts carry eventloom:// citations, and agents are told to trust only cited facts.

Decision record (condensed)

ADR	Decision	Status
1	Event-sourced JSONL over mutable state	active
2	Hybrid extraction: deterministic rules first, LLM fallback	active
3	Graph projection backend	superseded: embedded LadybugDB default; Neo4j sidecar opt-in
4	Hybrid retrieval (exact + BM25 + graph traversal + embeddings)	active
5	Pathlight observability integration	active, optional
6	MCP as the primary agent interface	active

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

2mo ago First seen · 101 lines · 1,417 tokens per session scan A c220d89d768b

Subscribe to this mod's changes

zaxy AGENTS.md is an instructions file published in the GitHub repository syndicalt/zaxy (17 stars, last pushed 2mo ago), licensed MIT. It adds 1,417 tokens to every session, about $0.0057 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.

Memory and context ai ai-agents ai-memory llm-tools

zaxy AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
zaxy AGENTS.mdsyndicalt/zaxy	Instructions file	17	2mo ago	MIT	A	1,417	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

zaxy: Instructions file for Codex