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/renderdraw/lens/claude-mdgit clone --depth 1 https://github.com/renderdraw/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.00838 | $0.00838 |
| Opus 5 | $0.00419 | $0.00419 |
| Sonnet 5 | $0.00168 | $0.00168 |
| Haiku 4.5 | $0.00084 | $0.00084 |
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RenderDraw Lens
Chrome extension for universal visual feedback, video direction, and QA assertions across the RenderDraw stack.
Architecture
- Manifest V3 Chrome extension with content script, service worker, side panel, and popup
- Content Script (
src/content/): Element selection engine, annotation popup, hover/click overlay - Service Worker (
src/background/): Session persistence (IndexedDB), MCP message relay, tab capture - Side Panel (
src/sidepanel/): Annotation list, project context, export (Markdown/JSON/Playwright/Remotion/clipboard) - Popup (
src/popup/): Lens toggle, mode selector, side panel opener - MCP Bridge (
src/mcp-bridge/): Standalone HTTP server (port 4848) for Claude Code integration - Shared (
src/shared/): RAF schema, constants, storage, serializers
Build
npm install
npm run build # Build extension to dist/
npm run dev # Watch mode
npm run typecheck # Type checking
npm run mcp # Start MCP bridge server on port 4848
Load dist/ as an unpacked extension in Chrome (chrome://extensions → Developer mode → Load unpacked).
Build System
Vite with inlineContentScript plugin. Post-build, shared chunk imports are inlined into content.js (wrapped in IIFE) and background.js because Chrome MV3 content scripts don't support ES module imports.
RAF Schema
All annotations use the RenderDraw Annotation Format (RAF) defined in src/shared/raf-schema.ts. Three modes:
- Feedback: Visual bug reports with element selection, computed styles, component trees
- Video Direction: Cinematic sequences with actions (zoom, pan, highlight), timing, narration
- QA Assertion: Visual regression specs with Playwright selectors and expected values
Styling
All UI uses the Journeys dark theme: #0a0a0f background, #FFD700 gold accents, #14B8A6 teal secondary, DM Sans typography. Design tokens in src/shared/constants.ts.
Content Script Injection
Content scripts auto-inject on new page loads via manifest.json. For pages open before extension install, both the popup and service worker use chrome.scripting.executeScript() as a fallback — try messaging, catch the error, inject programmatically, retry.
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 · 71 lines · 838 tokens per session scan A 3013cda793a2
lens CLAUDE.md is an instructions file published in the GitHub repository renderdraw/lens (4 stars, last pushed 5mo ago), licensed MIT. It adds 838 tokens to every session, about $0.0042 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
opentabs AGENTS.md
Instructions for opentabs-dev/opentabs, covering project instructions for codex, project overview, architecture, you are connected to this project's mcp server and workflow skills.
vBookmarks AGENTS.md
Instructions for windviki/vBookmarks, covering agents.md, project overview, repository layout, build, test, and development commands and load for development.
band-play AGENTS.md
Instructions for borbiuk/band-play, covering repository agents (bandcamp play), product, architecture (mv3), messaging and build and manifest constraints.
band-play CLAUDE.md
Instructions for borbiuk/band-play, covering claude code — bandcamp play, working rules, detailed rules (read on demand) and skills and commands.
opentabs CLAUDE.md
Instructions for opentabs-dev/opentabs, covering project instructions for claude, project overview, architecture, you are connected to this project's mcp server and workflow skills.
hanzi-browse CLAUDE.md
Claude Code instructions for hanzili/hanzi-browse, covering hanzi browse — architecture guide, what is hanzi browse?, architecture, key directories and value propositions.