lorekit CLAUDE.md

Project instructions for Lorekit, a TypeScript toolkit that lets an AI build and maintain a personal knowledge base. They tell the coding agent how to restore project context and verify changes.

In plain words
What is it for?
Use them when modifying Lorekit, routing a task to the right module, continuing work from an earlier session, or verifying changed files.
Why use it?
They give the agent the project’s rules and the correct reading order, reducing missed context and incomplete checks.

Instructions file

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/gyf0311/lorekit/claude-md
Clone the repo
git clone --depth 1 https://github.com/GYF0311/lorekit
Per session 151 This file is loaded in full into every session.
When invoked 151 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.00151 $0.00151
Opus 5 $0.00076 $0.00076
Sonnet 5 $0.00030 $0.00030
Haiku 4.5 $0.00015 $0.00015

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

Security

Grade A, and why

lorekit 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 · 16 lines

What it actually says

@./AGENTS.md

CMAP 项目地图

本仓库已接入 CMAP。Claude Code 仍应先遵守 AGENTS.md;需要续接项目上下文时,按以下顺序读取:

  1. .context/CHECKPOINT.md
  2. .context/MAP.md
  3. cmap route "<task>"
  4. 命中的 .context/modules/<module>.md
  5. 收尾跑 .context/VERIFY.md 中的相关命令,至少 cmap verify --changed

.context 正文默认中文;frontmatter key、module id、命令、路径和代码标识符保留英文。

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 · 16 lines · 151 tokens per session scan A 6a3f2280959a

Subscribe to this mod's changes

lorekit CLAUDE.md is an instructions file published in the GitHub repository GYF0311/lorekit (5 stars, last pushed 1mo ago), licensed MIT. It adds 151 tokens to every session, about $0.0008 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.

Related

Other instructions, from other repositories