Overview

A CLAUDE.md or AGENTS.md starts small. Then every incident, convention and "always remember to…" gets appended, skills and agents pile up, and nobody knows what the configuration weighs anymore. In this project I wanted to make that growth visible: Strata replays the Git history of a repository and shows what its agent configuration weighs today, when it grew, and which files drove it.

Key Features

• Timeline: Stored instruction tokens across the branch history, split by category, from root instructions to skills and agents.
• Treemap: The configuration at any revision, so the file eating most of the budget is the biggest rectangle.
• Instruction age: How long the instruction text has stayed, so old rules that nobody revisits stand out.
• Comparison: Token and file changes between any two revisions, by provider, category and file.
• Multi-agent: A view per coding agent, with shared files like AGENTS.md counted once.
• Pull requests: A GitHub Action that shows what a pull request adds to the configuration before it merges.
• Private by default: Read-only and offline. Reports hold measurements, never the text of the instructions, and a shareable mode replaces names and paths with aliases.

Technologies Used

• TypeScript and Node.js: For the CLI, published on npm.
• Git: Strata reads the stored files of each commit, never the working tree.
• HTML and SVG: For a single offline report, and an image of the history to embed in a README.

Challenges and Learnings

The first challenge was to be honest about what is measured: Strata counts the text stored in Git, not what an agent loaded in a session or what was billed. Second challenge was to replay a long history fast, from a single streamed git log that reads file contents only when the measurement needs them. Third challenge was to keep the report a single offline file: storing each revision as a change instead of a full file list took one report from 57 MB down to 1.5 MB.

Outcome

Run it on your own repository and see how your agent context grew.