Borrowing it
Nothing to install: this file belongs to chigichan24/crune. 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/chigichan24/crune/main/CLAUDE.mdgit clone --depth 1 https://github.com/chigichan24/cruneWrote 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/chigichan24/crune/claude-md)<a href="https://agentmods.dev/instructions/chigichan24/crune/claude-md"><img src="https://agentmods.dev/badge/instructions/chigichan24/crune/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.04482 | $0.04482 |
| Opus 5 | $0.02241 | $0.02241 |
| Sonnet 5 | $0.00896 | $0.00896 |
| Haiku 4.5 | $0.00448 | $0.00448 |
Grade A, and why
crune 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 6d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project Overview
crune is a static web dashboard that visualizes Claude Code session logs. It consists of two parts:
- Data pipeline (
scripts/analyze-sessions.ts+scripts/knowledge-graph-builder.ts): Reads JSONL session files, extracts structured data, builds a semantic knowledge graph, and outputs JSON files topublic/data/sessions/. - Frontend (
src/): React SPA that loads the generated JSON and renders three views --- Overview, Session Playback, and Knowledge Graph.
Build & Run
npm install
npm run analyze-sessions # Generate data from ~/.claude/projects/
npm run dev # Vite dev server at localhost:5173
npm run build # tsc -b && vite build -> dist/
npm run lint # ESLint
npm run skill-server # Local synthesis server at localhost:3456
npm run dev:full # skill-server + Vite dev server together
Architecture
- No routing library ---
App.tsxmanages view state viauseState<ViewMode>(overview | playback | knowledge) - No state management library --- Data flows through props from
App.tsxdown. Each view fetches its own data via custom hooks (useSessionIndex,useSessionDetail,useSessionOverview) - Plain CSS --- Each component has a co-located
.cssfile. Global CSS variables are insrc/index.css(colors, fonts, shadows) - Session playback opens as a right-side drawer overlay, not a separate route
Key Conventions
- UI text is in Japanese (commit
abc92e1) - Color variables have semantic roles:
--accent(amber, interactive),--brand(amber, logo only — unified with accent),--success/warning/danger(status),--chart-1..6(data visualization) - Tool call display logic is centralized in
ToolCallBlock.tsxwith per-tool rendering (Bash, Edit, Write, Read, Grep, Glob, Agent) - Expand/collapse pattern:
useState(false)+ conditional render (no animation), seeSubagentBranch.tsx
Data Pipeline Details
analyze-sessions.ts reads from ~/.claude/projects/ by default. Override with --sessions-dir and --output-dir flags.
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.
- 6d ago First seen · 211 lines · 4,482 tokens per session scan A e56a7615edaf
crune CLAUDE.md is an instructions file published in the GitHub repository chigichan24/crune (23 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 4,482 tokens to every session, about $0.0224 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.