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/daaain/claude-code-log/claude-mdgit clone --depth 1 https://github.com/daaain/claude-code-logWhat 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.01366 | $0.01366 |
| Opus 5 | $0.00683 | $0.00683 |
| Sonnet 5 | $0.00273 | $0.00273 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade A, and why
claude-code-log 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Log
A Python CLI tool that converts Claude Code transcript JSONL files into readable HTML format.
Project Overview
This tool processes Claude Code transcript files (stored as JSONL) and generates clean, minimalist HTML pages with comprehensive session navigation and token usage tracking. It's designed to create a readable log of your Claude interactions with rich metadata and easy navigation.
Key Features
- Interactive TUI (Terminal User Interface): Browse and manage Claude Code sessions with real-time navigation, summaries, and quick actions for HTML export and session resuming
- Project Hierarchy Processing: Process entire
~/.claude/projects/directory with linked index page - Individual Session Files: Generate separate HTML files for each session with navigation links
- Session Navigation: Interactive table of contents with session summaries and quick navigation
- Token Usage Tracking: Display token consumption for individual messages and session totals
- Runtime Message Filtering: JavaScript-powered filtering to show/hide message types
- Interactive Timeline: vis-timeline visualization with click-to-scroll navigation
- Date Range Filtering: Filter messages using natural language (e.g., "today", "yesterday")
- Markdown Rendering: Server-side markdown with syntax highlighting using mistune
Usage
# Process all projects (default)
claude-code-log
# Interactive TUI
claude-code-log --tui
# Single file/directory
claude-code-log path/to/transcript.jsonl
# With browser open
claude-code-log --open-browser
# Date filtering (natural language)
claude-code-log --from-date "yesterday" --to-date "today"
claude-code-log --from-date "last week"
Output Files Generated:
~/.claude/projects/index.html- Master index with project cards~/.claude/projects/project-name/combined_transcripts.html- Combined project page~/.claude/projects/project-name/session-{id}.html- Individual session pages
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 · 133 lines · 1,366 tokens per session scan A 50cdf3bcbbc2
claude-code-log CLAUDE.md is an instructions file published in the GitHub repository daaain/claude-code-log (1,201 stars, last pushed 2d ago), licensed MIT. It adds 1,366 tokens to every session, about $0.0068 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-30.
Other instructions, from other repositories
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).
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.
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.