Borrowing it
Nothing to install: this file belongs to aotakeda/local-lens. 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/aotakeda/local-lens/main/CLAUDE.mdgit clone --depth 1 https://github.com/aotakeda/local-lensWrote 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/aotakeda/local-lens/claude-md)<a href="https://agentmods.dev/instructions/aotakeda/local-lens/claude-md"><img src="https://agentmods.dev/badge/instructions/aotakeda/local-lens/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.01324 | $0.01324 |
| Opus 5 | $0.00662 | $0.00662 |
| Sonnet 5 | $0.00265 | $0.00265 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
local-lens CLAUDE.md scanned grade A with 1 finding 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 8d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **Process Spawn**: Uses Node.js child_process.spawn for reliable process management How it starts
The opening of the file, as written. The whole thing — 151 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.
Project Overview
Local Lens is a comprehensive 100% local development monitoring tool that captures both browser and server logs for LLM analysis. It consists of a Chrome extension for browser monitoring, a CLI tool for universal backend log capture, and an HTTP/MCP server for data access. The system is completely local with no external connections.
Architecture
High-Level Structure
- Chrome Extension: Manifest v3 extension with service worker and content scripts for browser monitoring
- CLI Tool: Universal process wrapper for backend log capture (any framework)
- Local Server: HTTP/MCP server running on fixed port 27497
- SQLite Database: Local persistence with intelligent filtering and circular buffer (10k entries)
- Monorepo: Root workspace managing server, extension, and CLI subprojects
Key Components
cli/: Universal CLI tool for server log capture from any backend frameworkextension/: Chrome extension with background service worker and dual content scriptsserver/: Node.js/Express server with MCP integration and SQLite storageserver/src/storage/: Database layer with LogStorage class and schema managementserver/src/mcp/: MCP server implementation for AI assistant accessserver/src/routes/: HTTP API endpoints for log retrieval and filtering
Development Commands
Common Operations
# Install dependencies and build everything
npm install
npm run build
# Development mode (watches files, rebuilds automatically)
npm run dev
# Run tests
npm test
# Run linting
npm run lint
# Run single test file
npm test -- --testPathPattern=integration.test.ts
Server-Specific Commands
# Run server tests only
npm run test:server
# Start server in development mode
npm run dev:server
# Build server only
npm run build:server
# Build MCP server only
npm run build:mcp
# Build both HTTP and MCP servers
npm run build:all
# Build CLI tool only
npm run build:cli
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.
- 8d ago First seen · 151 lines · 1,324 tokens per session scan A 3b4a7327909e
local-lens CLAUDE.md is an instructions file published in the GitHub repository aotakeda/local-lens (7 stars, last pushed 1y ago), licensed MIT. It adds 1,324 tokens to every session, about $0.0066 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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.