read-once: A Claude Code Hook That Prevents Redundant File Reads

A developer has created a PreToolUse hook called read-once that addresses Claude Code's tendency to repeatedly read the same files during a session, which consumes unnecessary tokens.
The Problem and Solution
Claude Code often re-reads files it already has in context. For example, opening a 500-line file, making a small edit, and having Claude read the entire file again costs approximately 2,000+ tokens per read. In typical sessions, the same files might be read 5-10 times.
The read-once hook tracks which files Claude has read in the current session. When Claude tries to re-read an unchanged file, the hook blocks it and displays a message like: "read-once: config.rs (~3,400 tokens) already in context (read 4m ago, unchanged). Session savings: ~12,000 tokens."
How It Works
- On first read: Records the file path, modification time, and timestamp, then allows the read normally.
- On re-read of unchanged file: Blocks the read since Claude already has the content.
- On re-read of changed file: Instead of allowing a full re-read, the hook computes the diff and returns only what changed. Claude already has the old version in context and just needs the delta. For a 500-line file where 3 lines changed, this uses ~30 tokens instead of ~2,000, saving 80-95% on file iterations.
Features and Configuration
The tool is TTL-aware with cache entries expiring after 20 minutes (configurable). After expiration, re-reads are allowed because Claude may have compacted the context and lost earlier content.
Configuration is done via environment variables:
READ_ONCE_TTL=1200- seconds before cache expires (default 20 min)READ_ONCE_DIFF=1- enable diff modeREAD_ONCE_DIFF_MAX=40- max diff lines before falling back to full re-readREAD_ONCE_DISABLED=1- turn it off entirely
Technical Details
The entire tool is approximately 250 lines of bash with zero dependencies beyond jq and diff. It's MIT licensed and installs by adding itself to your .claude/settings.json hooks.
The developer built this tool because they run Claude Code in an autonomous loop where token costs add up quickly. The diff mode alone reportedly cut their per-session token usage by about 30%.
📖 Read the full source: r/ClaudeAI
👀 See Also

Claude File History: VS Code Extension for Tracking Claude Code Sessions
A VS Code extension called Claude File History tracks every Claude Code session that touched your files, allowing you to find past conversations, preview what was discussed, and resume conversations with a double-click.

SideX: A Tauri-Based Port of Visual Studio Code
SideX is a port of Visual Studio Code that replaces Electron with Tauri, using a Rust backend and the OS's native webview. The project claims the same architecture with 96% smaller size, with core editing and terminal functionality currently working.

Lobster Cage: Dockerized Security Environment for Self-Hosting OpenClaw on Raspberry Pi
A developer built Lobster Cage, a Docker Compose environment with restricted outbound access and proxy-based routing to run OpenClaw securely on a Raspberry Pi for experimentation.

pxpipe: Cut Claude Code Token Usage 60% by Rendering Context as Images
pxpipe is a local proxy that renders bulky context (system prompts, tool docs, history) into compact PNGs, cutting input tokens ~10x and costs ~60% on token-dense workloads.