What is lory CLAUDE.md?

A set of project instructions for Lory, a tool that records why code and design decisions were made. It also defines commit details, checks, and use of the Beads issue tracker.

Use it before changing code, to inspect constraints and past decisions, and after committing, to check the required record format.

It helps developers understand the reasoning behind existing code and avoid repeating approaches that were already rejected. It also keeps commit records consistent and reviewable.

How jankowskim/lory configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jankowskim/lory. 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/jankowskim/lory/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/jankowskim/lory

Made for: Claude Code.

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/jankowskim/lory/claude-md/github.svg)](https://agentmods.dev/instructions/jankowskim/lory/claude-md)

Your own site

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

Per session 748 This file is loaded in full into every session.

When invoked 748 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.00748	$0.00748
Opus 5.5	$0.00299	$0.00299
Sonnet 5.5	$0.00150	$0.00150
Haiku 4.5	$0.00075	$0.00075

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

Security

Grade A, and why

lory 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 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.

CLAUDE.md · 92 lines

How it starts

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

Lory — Structured Decision Records

This repository uses Lory for structured decision records.

Before Modifying Code

Run lory context <path> to understand why the code is shaped this way.
Run lory rejected <path> to avoid re-exploring dead ends.

Commit Format

Every commit must explain WHY, not WHAT. Use Lory trailers:

Short description of WHY this change was made

Constraint: Any rules this change must follow
Rejected: Alternative approach | why it was rejected
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Warning for future maintainers
Tested: What was tested
Not-tested: What was not tested

Run lory validate --count 1 after committing to verify format.

Commands

lory context <path>        # Full decision context for a file/directory
lory constraints <path>    # Active constraints affecting this code
lory rejected <path>       # Previously rejected alternatives
lory directives <path>     # Forward-looking warnings from past authors
lory stale                 # Detect outdated assumptions
lory review --base main    # Check changes against decision context
lory validate --count 5    # Check recent commits for proper format
lory export [paths]        # Export decision context as JSONL or text
lory preflight             # Combined pre-PR check (validate+stale+coverage+review)

Beads Issue Tracker

This project uses bd (beads) for issue tracking. Run bd prime to see full workflow context and commands.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --claim  # Claim work
bd close <id>         # Complete work

Rules

Use bd for ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists
Run bd prime for detailed command reference and session close protocol
Use bd remember for persistent knowledge — do NOT use MEMORY.md files

Read the full file on GitHub · 92 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 · 92 lines · 748 tokens per session scan A 427b2149f3c3

Subscribe to this mod's changes

lory CLAUDE.md is an instructions file published in the GitHub repository jankowskim/lory (2 stars, last pushed 6mo ago), licensed MIT. It adds 748 tokens to every session, about $0.0030 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-31.

commit-history decision-records

lory CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lory CLAUDE.mdjankowskim/lory	Instructions file	2	6mo ago	MIT	A	748	Claude Code
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

lory: Instructions file for Claude Code