Borrowing it
Nothing to install: this file belongs to milkoor/causetrace. 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/milkoor/causetrace/main/CLAUDE.mdgit clone --depth 1 https://github.com/milkoor/causetraceWrote 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/milkoor/causetrace/claude-md)<a href="https://agentmods.dev/instructions/milkoor/causetrace/claude-md"><img src="https://agentmods.dev/badge/instructions/milkoor/causetrace/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/milkoor/causetrace/claude-md"><img src="https://agentmods.dev/badge/instructions/milkoor/causetrace/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.03240 | $0.03240 |
| Opus 5.5 | $0.01296 | $0.01296 |
| Sonnet 5.5 | $0.00648 | $0.00648 |
| Haiku 4.5 | $0.00324 | $0.00324 |
Grade A, and why
causetrace 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 1mo 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 — 205 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.
What causetrace does
causetrace is an Agent Runtime Observation primitive — it captures tool calls from coding agents (Claude Code, OpenCode, Aider, Continue.dev, Codex CLI, GitHub Copilot, Hermes Agent, DeepSeek Harness) and links them into causal trees and DAGs via parent_event_id chains. Instead of flat timelines, every event records why it happened, enabling replay, root-cause analysis, and behavior explanation.
Before making changes
Read docs/dependency-map.md first — it shows which modules depend on what.
Use it to assess change impact before modifying any file.
Build & test
# Install (editable)
pip install -e .
# Run all tests
python -m pytest tests/ -v
# Run a single test
python -m pytest tests/test_invariants.py::test_causality_chain_links -v
# Run the installed first-run path
causetrace demo
CLI
causetrace timeline [session_id] # Flat chronological view
causetrace tree [session_id] # Causal parent→child tree
causetrace tree [session_id] --quality # Tree with causal quality report
causetrace tree [session_id] --compress # Compress consecutive same-tool runs ([×N])
causetrace graph [session_id] # Multi-parent DAG (fan-in)
causetrace sessions # List recorded sessions
causetrace export <session_id> # Export as JSON
causetrace replay [session_id] # Replay trace with provenance
causetrace why <session_id> <eid> # Trace causal chain from event
causetrace enrich-sessions # List Claude Code project sessions
causetrace enrich <session_id> [--save] # Enrich from Claude Code project session
causetrace enrich-opencode-sessions # List OpenCode DB sessions
causetrace enrich-opencode <id> [--save] # Enrich from OpenCode DB session
causetrace enrich-codex-sessions # List Codex CLI rollout sessions
causetrace enrich-codex <id> [--save] # Enrich from Codex CLI rollout session
causetrace enrich-hermes-sessions # List Hermes Agent sessions (state.db)
causetrace enrich-hermes <id> [--save] # Enrich from Hermes Agent SQLite session
causetrace enrich-dsh-sessions # List DeepSeek Harness (DSH) sessions
causetrace enrich-dsh <id> [--save] # Enrich from DSH session log (native causality)
causetrace dsh-tree [<id>] [--home] [--json] # DSH session-level delegation forest (parentSession headers)
causetrace opencode [--save] # Scan OpenCode logs
causetrace aider [--save] -- [args] # Run aider with tracing
causetrace continue [--save] # Scan Continue.dev logs
causetrace codex [--save] # Legacy scan path; prefer enrich-codex
causetrace copilot [--save] # Scan GitHub Copilot agent logs
causetrace doctor # Diagnose agent configuration and data sources
causetrace stats [session] # Structural session statistics
causetrace roots [session] # Root events with downstream metrics
causetrace critical-path [session] # Longest root-to-leaf causal chain
causetrace fidelity [session] [--json] # Native links vs temporal inference (ground-truth runtimes)
causetrace patterns [session] # Repeated tool patterns & transitions
causetrace patterns [session] --csv # Causal transitions as CSV
causetrace validate [session] # Check JSONL/references/cycles
causetrace validate --all # Validate all stored sessions
causetrace annotate <session> [...] # Store sidecar metadata
causetrace compare <a> <b> # Compare session topology
causetrace demo # Create an inspectable sample trace
causetrace install-claude-hook # Configure recording hooks safely
causetrace uninstall-claude-hook # Remove only managed hooks
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.
- 1mo ago Changed · +1 lines · +62 tokens per session e0cf32cef869
- 1mo ago Changed · +10 lines · +320 tokens per session b1fd267d7365
- 2mo ago First seen · 194 lines · 2,858 tokens per session scan A d732f489000d
causetrace CLAUDE.md is an instructions file published in the GitHub repository milkoor/causetrace (2 stars, last pushed 1mo ago), licensed MIT. It adds 3,240 tokens to every session, about $0.0130 per session on Opus 5.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-31.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.