Borrowing it
Nothing to install: this file belongs to Sardor-M/lumen. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Sardor-M/lumen/main/CLAUDE.mdgit clone --depth 1 https://github.com/Sardor-M/lumenWrote 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.
[](https://agentmods.dev/instructions/sardor-m/lumen/claude-md)<a href="https://agentmods.dev/instructions/sardor-m/lumen/claude-md"><img src="https://agentmods.dev/badge/instructions/sardor-m/lumen/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.01272 | $0.01272 |
| Opus 5 | $0.00636 | $0.00636 |
| Sonnet 5 | $0.00254 | $0.00254 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
lumen 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lumen — Project Rules
What is Lumen
Local-first knowledge compiler. Ingest articles/papers/videos → chunk → store in SQLite → search via BM25 → compile into knowledge graph via LLM.
Repo structure
Monorepo with Turborepo + pnpm workspaces.
lumen/
├── apps/
│ ├── cli/ — The CLI and MCP server (the engine)
│ ├── web/ — Next.js 15 web UI with Better Auth + Zod
│ └── extension/ — Browser extension (placeholder)
├── docs/ — PRODUCT-ROADMAP.md, etc.
├── turbo.json
├── pnpm-workspace.yaml
└── package.json
Commands (run from repo root)
pnpm dev # turbo dev — runs all apps in parallel
pnpm build # turbo build — builds all apps
pnpm lint # turbo lint
pnpm test # turbo test
pnpm format # prettier on all apps
pnpm --filter lumen-kb dev # CLI only
pnpm --filter @lumen/web dev # web only
pnpm --filter @lumen/web build # web build
Hard Rules (apply to all apps)
typenotinterface. Always. No exceptions.- **
/** JSDoc \*/not//**. Every comment is JSDoc style. .jsextensions in all relative imports (inapps/cli/). ESM requires it.import typefor type-only imports.- No classes. Plain functions and types only.
- No default exports — EXCEPT in
apps/web/for Next.js framework files (page.tsx,layout.tsx,error.tsx,loading.tsx,not-found.tsx,route.ts,next.config.ts). Everywhere else uses named exports. - No enums. Use union types:
type Foo = 'a' | 'b' | 'c' - No
any. Useunknownor specific types. - Prefix unused params with
_.
App-specific rules
apps/cli/
- No
console.login commands. Uselog.info/success/warn/error/heading/table/dim. - No
process.exit(). Setprocess.exitCode = 1instead. .jsextensions in all relative imports.
apps/web/
- Default exports allowed for Next.js framework files only (see list above). All library code (
src/lib/*,src/components/*) uses named exports. - Server components by default. Add
'use client'only when you need interactivity. - Zod for input validation — all form inputs and API route bodies go through a Zod schema in
src/lib/schemas.ts. - Better Auth session check via
auth.api.getSession({ headers: await headers() })in server components. Redirect unauthenticated users from protected routes. - No
.jsextension in relative imports — Next.js handles it. - Inline
export functionfor all UI components. Never use bottomexport { ... }blocks. Writeexport function Button(...)notfunction Button(...) ... export { Button }. export constfor CVA variants — writeexport const buttonVariants = cva(...)inline.- shadcn base-ui uses
renderprop, NOTasChild. To render a component as a Link:<SidebarMenuButton render={<Link href="..." />}>. Do NOT useasChild— it leaks to DOM elements. cn()from@/lib/utilsfor all className merging.
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.
- 6d ago First seen · 103 lines · 1,272 tokens per session scan A 9f29dc289d19
lumen CLAUDE.md is an instructions file published in the GitHub repository Sardor-M/lumen (11 stars, last pushed 2mo ago), licensed MIT. It adds 1,272 tokens to every session, about $0.0064 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.