agent-knowledge AGENTS.md

A project guide for agent-knowledge, a long-term memory system for AI assistants. It turns conversations and documents into traceable facts, combines them into a shared record, keeps a timeline, and flags contradictions.

In plain words
What is it for?
Use it to answer why earlier decisions were made, merge facts from several sources, preserve project conventions, and retrieve memory through its MCP server.
Why use it?
It helps an assistant recover past decisions and preferences across sessions while showing where each fact came from. It also explains when this system is unnecessary, such as for one-time document lookup.

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/yucx-go/agent-knowledge/agents-md
Clone the repo
git clone --depth 1 https://github.com/yucx-go/agent-knowledge

Made for: Codex, OpenCode.

Per session 1,083 This file is loaded in full into every session.
When invoked 1,083 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.01083 $0.01083
Opus 5 $0.00541 $0.00541
Sonnet 5 $0.00217 $0.00217
Haiku 4.5 $0.00108 $0.00108

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

Security

Grade A, and why

agent-knowledge 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 · 131 lines

How it starts

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

AGENTS.md

Project guide for AI agents (Claude Code, Codex, Cursor, custom agents). Human readers should start at README.md.

What this project is

agent-knowledge is long-term memory and a knowledge base for AI agents: raw conversations and documents → Claim + Evidence extraction → merged into Compiled Truth → append-only timeline. Every fact is traceable to source, timestamp, and confidence, with contradiction detection on top.

Position: it is compiled memory — not RAG, not a KV preference cache.

When you (an agent) should use it

  • The user asks "why did we decide X back then?" — needs timeline and decision context
  • Multiple sources about the same entity need to be merged and reconciled
  • Facts need to persist across sessions (user preferences, project conventions, prior decisions)
  • The answer must be explainable with source provenance, not just "vector similarity"

Skip it for:

  • One-shot retrieval (plain RAG is lighter)
  • Real-time event streams (this is the knowledge layer, not an event bus)

Quickest path to use

Option 1: MCP server (recommended for agent integration)

{
  "mcpServers": {
    "agent-knowledge": {
      "command": "ak",
      "args": ["mcp", "/absolute/path/to/vault"]
    }
  }
}

Drop this into .claude/settings.json, .cursor/mcp.json, or any MCP-aware client config. Full tool list is in docs/mcp-integration.md.

Option 2: CLI

compiled-memory is the PyPI distribution; agent_knowledge is the Python module.

pip install compiled-memory
ak init   /path/to/vault
ak ingest /path/to/vault --file notes.md
ak query  /path/to/vault "why did we pick React?"

Option 3: Python API

from agent_knowledge import Vault, Compiler, SearchEngine

vault = Vault("/path/to/vault")
vault.init()

compiler = Compiler(vault)
compiler.ingest("We picked React over Vue.", title="Frontend decision")

engine = SearchEngine(vault)
for hit in engine.search("why React?", top_k=5):
    print(hit.title, hit.score)

Read the full file on GitHub · 131 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 · 131 lines · 1,083 tokens per session scan A 0265cbe745a7

Subscribe to this mod's changes

agent-knowledge AGENTS.md is an instructions file published in the GitHub repository yucx-go/agent-knowledge (3 stars, last pushed 3mo ago), licensed MIT. It adds 1,083 tokens to every session, about $0.0054 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.