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.
npx agentmods add instructions/maliming/lens/claude-mdgit clone --depth 1 https://github.com/maliming/LensWhat 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 | $0.05458 | $0.05458 |
| Opus 5 | $0.02729 | $0.02729 |
| Sonnet 5 | $0.01092 | $0.01092 |
| Haiku 4.5 | $0.00546 | $0.00546 |
Grade A, and why
Lens 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.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this is
Lens is an Electron desktop app that browses, searches, and resumes local Claude Code (~/.claude/projects/*.jsonl) and OpenAI Codex (~/.codex/sessions/**/*.jsonl) session history. The package name in package.json is lens.
Common commands
npm install
npm run dev # Vite (http://localhost:5173) + Electron in parallel
npm run typecheck # tsc --noEmit (run before any commit)
npm run check:i18n # scripts/check-i18n.mjs — diffs each locale vs en
npm run build # typecheck + Vite build → dist/ (does NOT package)
npm run preview # run Electron against built dist/
npm run dist:mac # release/Lens-<ver>-(arm64|x64).zip
npm run dist:win # release/Lens-<ver>-win.zip
npm run dist:linux # release/Lens-<ver>-linux-x86_64.AppImage
npm run build:icon # regenerate build/icon.{icns,ico,png} from icon.svg
DEMO_BUILD=1 npm run dist:mac # screenshot-ready build with fake data forced on
There are no tests and no linter configured. npm run build runs tsc --noEmit && vite build. npm run check:i18n is NOT in build — running it reveals real gaps (non-English locales miss ~200 keys each); wire to CI only after you've committed to translating, otherwise it'll fail every build.
Renderer hot-reloads under npm run dev. Main-process edits (electron/main.cjs) require a full restart — there is no main-process reload. Session cache manifests (sessions-cache-claude.json / sessions-cache-codex.json, plus bounded shards when a source exceeds the single-file limit) under the platform userData directory survive across restarts. Parser/cache schema changes require a versioned migration in electron/lib/sessions-cache.cjs; do not rely on manually deleting caches.
High-level architecture
Two-process boundary
electron/main.cjs(Node) — all filesystem IO, JSONL parsing, sub-process spawning (terminal launchers,claude/codexCLI probes), persistence (favorites.json/excludes.json/aliases.json/ per-source session caches /app-prefs.jsonunderapp.getPath('userData')).src/(React 18 + TypeScript + Vite + Tailwind) — pure renderer. No Node access. Talks to main only viawindow.api.*.electron/preload.cjs—contextBridge.exposeInMainWorld('api', ...). This is the IPC contract; any new feature that crosses the boundary needs an entry here + a matchingipcMain.handleinmain.cjs+ a typed signature insrc/types.tsunderdeclare global { interface Window { api: { ... } } }.
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.
- 2d ago First seen · 229 lines · 5,458 tokens per session scan A 76a26232aee7
Lens CLAUDE.md is an instructions file published in the GitHub repository maliming/Lens (6 stars, last pushed 10d ago), licensed MIT. It adds 5,458 tokens to every session, about $0.0273 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
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.
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).
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.