What is lore AGENTS.md?

A workflow guide for Lore, a local searchable store of coding-agent session transcripts. It covers the command-line tool, the server connection, the SQLite database, search, indexing, privacy, and deletion.

Use it to add or change transcript search, storage adapters, privacy controls, deletion paths, command-line features, or the agent skill.

It explains how to make changes safely across Lore's related parts and how to verify behavior without relying on a graphical interface.

How jordanhindo/lore configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to jordanhindo/lore. 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/jordanhindo/lore/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/jordanhindo/lore

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/jordanhindo/lore/agents-md/github.svg)](https://agentmods.dev/instructions/jordanhindo/lore/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/jordanhindo/lore/agents-md"><img src="https://agentmods.dev/badge/instructions/jordanhindo/lore/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/jordanhindo/lore/agents-md"><img src="https://agentmods.dev/badge/instructions/jordanhindo/lore/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,407 This file is loaded in full into every session.

When invoked 2,407 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.02407	$0.02407
Opus 5.5	$0.00963	$0.00963
Sonnet 5.5	$0.00481	$0.00481
Haiku 4.5	$0.00241	$0.00241

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

Security

Grade A, and why

lore 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 · 239 lines

How it starts

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

Lore Agent Workflow

Lore is a local, full-fidelity, searchable memory store for agent session transcripts. Work here touches three product surfaces:

The TypeScript CLI and MCP server.
The SQLite store, adapters, search, indexing, redaction, and deletion paths.
The bundled agent skill under skills/lore.

Do not copy workflows from UI-heavy apps. Lore has no app frontend. Verification means CLI behavior, MCP parity, schema/write-path safety, adapter fidelity, privacy behavior, and skill behavior.

This repo follows a Matt Pocock-style agentic coding workflow. The rule is not "add ceremony." The rule is: keep the human in planning, slice work into large vertical tracer bullets, run implementation in fresh contexts, and review with fresh eyes before integration.

Workflow Levels

Use the light workflow for small work:

Read the relevant code/docs first.
Make the smallest scoped change that solves the request.
Run the relevant verification command.
Report what changed and what proved it.

Use the program workflow for large bodies of work:

New product surfaces such as lore:recall, lore:brief, typed cards, privacy audit, new adapters, or new retrieval flows.
Store, schema, search, ranking, redaction, deletion, or compatibility changes.
Cross-agent skill bundle changes.
Multi-issue work that should land as one final PR.
Anything where stale memory, privacy, or broken retrieval would be costly.

Do not force the program workflow onto typo fixes, tiny docs polish, simple formatting changes, or narrow bug fixes with an obvious test seam.

Program Workflow

Alignment before planning. For ambiguous work, use a grill/alignment step before writing the PRD. The goal is shared design concept, not a document for its own sake. If the answer can be discovered from the codebase, discover it instead of asking Jordan.
One PRD per large body of work. Write or update one PRD under docs/PRD-*.md. The PRD is the destination document: problem, solution, extensive user stories, implementation decisions, testing decisions, seams, out of scope, and notes. It should shape the whole program, not one tiny issue.

Read the full file on GitHub · 239 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 · 239 lines · 2,407 tokens per session scan A 11e4e8d4475c

Subscribe to this mod's changes

lore AGENTS.md is an instructions file published in the GitHub repository jordanhindo/lore (16 stars, last pushed 4mo ago), licensed MIT. It adds 2,407 tokens to every session, about $0.0096 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.

Building agents Research

lore AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lore AGENTS.mdjordanhindo/lore	Instructions file	16	4mo ago	MIT	A	2,407	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

lore: Instructions file for Codex