Borrowing it
Nothing to install: this file belongs to monk1337/clicodelog. 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/monk1337/clicodelog/main/CLAUDE.mdgit clone --depth 1 https://github.com/monk1337/clicodelogWrote 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/monk1337/clicodelog/claude-md)<a href="https://agentmods.dev/instructions/monk1337/clicodelog/claude-md"><img src="https://agentmods.dev/badge/instructions/monk1337/clicodelog/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.01558 | $0.01558 |
| Opus 5 | $0.00779 | $0.00779 |
| Sonnet 5 | $0.00312 | $0.00312 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
clicodelog 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 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.
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 — 134 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.
Commands
# Install from source (editable, changes take effect immediately)
uv pip install -e .
# Run the app
clicodelog
# or without installing:
uv run python -m clicodelog.cli
# Common flags
clicodelog --port 8080 # custom port (default: 6126)
clicodelog --no-sync # skip initial sync (faster startup for dev)
clicodelog --debug # debug logging to console as well as file
# Tests
uv run python -m pytest tests/ -q
# Build for distribution
uv build # produces dist/*.whl and dist/*.tar.gz
Never test against port 6126 — that is the user's running instance. Use a
different port (--port 6231).
Architecture
clicodelog is a local-first web app that backs up AI agent logs to
~/.clicodelog/data/ and serves them via a FastAPI browser UI.
There are three layers, and keeping them straight is the main thing:
- The backup (
sync.py) — an additive, never-deleting copy of each source tool's log directory, made with APFSclonefileso it costs almost no disk. This is the durable source of truth. It deliberately keeps files the source tool has pruned, so it must never delete and never replace a file non-atomically. - The metadata index (
search_index.py) — one small record per session, in~/.clicodelog/search_index.json. Derived state, rebuildable at any time. Session and project listings are served from here, not from the files. - The content index (
fts.py) — SQLite FTS5 over message bodies in~/.clicodelog/fts.db. Also derived. Optional: it is only built on request, and refuses to build if it would not fit on disk.
File map
clicodelog/
├── cli.py # argparse entry point -> server.run_server()
├── app.py # FastAPI setup, cache policy, template routes
├── config.py # SOURCES dict, DATA_DIR, APP_DATA_DIR, constants
├── logging_setup.py # rotating file log at ~/.clicodelog/clicodelog.log
├── storage.py # atomic JSON read/write, quarantine, disk checks
├── scan.py # ONE-PASS session metadata extraction (all 3 sources)
├── sync.py # additive clone-backup, background + initial sync
├── search_index.py # metadata index; backs listings, projects and search
├── fts.py # SQLite FTS5 content index, query sanitizer
├── sessions.py # session listings (from the index)
├── projects.py # project listings (from the index)
├── conversation.py # conversation loading, pagination, LRU cache
├── bookmarks.py # user-authored bookmarks (atomic, locked)
├── metadata.py # custom project names/tags (atomic, locked)
├── utils.py # path ids, id validation, per-source helpers
├── server.py # port handling, startup, uvicorn
├── parsers/ # claude.py, codex.py, gemini.py
├── routes/ # projects, search, export, sync, sources, bookmarks, stats
├── static/css/*.css
├── static/js/*.js # vanilla, no build step; vendor/ holds marked+purify+hljs
└── templates/ # index.html, view.html
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 · 134 lines · 1,558 tokens per session scan A 644631660622
clicodelog CLAUDE.md is an instructions file published in the GitHub repository monk1337/clicodelog (49 stars, last pushed 14d ago), licensed MIT. It adds 1,558 tokens to every session, about $0.0078 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
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.