---
title: "Comment by Apps by Mo on \"Clogmeter is live on Product Hunt: see what your agent instruction files cost\" | Hashnode"
description: "Good problem to measure. What helped me most with Claude Code was splitting the file that loads every session from everything else: my memory index is one line"
url: "https://hashnode.com/posts/clogmeter-is-live-on-product-hunt-see-what-your-agent-instruction-files-cost/6af2d0a15d456961fae8fe32/comment/6af318ab8d0998379daa40ba"
---

[Discussion](https://hashnode.com/posts/clogmeter-is-live-on-product-hunt-see-what-your-agent-instruction-files-cost/6af2d0a15d456961fae8fe32)

Comment [Clogmeter is live on Product Hunt: see what your agent instruction files cost](https://hashnode.com/posts/clogmeter-is-live-on-product-hunt-see-what-your-agent-instruction-files-cost/6af2d0a15d456961fae8fe32)

[Apps by Mo](https://hashnode.com/@appsbymo)

[Nov 10](https://hashnode.com/posts/clogmeter-is-live-on-product-hunt-see-what-your-agent-instruction-files-cost/6af2d0a15d456961fae8fe32/comment/6af318ab8d0998379daa40ba)

Good problem to measure. What helped me most with Claude Code was splitting the file that loads every session from everything else: my memory index is one line per note, and a note is only read when it is relevant. The index stays small while the notes grow. Does Clogmeter tell apart files read on every turn from ones loaded on demand?

[Clogmeter](https://hashnode.com/@clogmeter)

[Nov 10](https://hashnode.com/posts/clogmeter-is-live-on-product-hunt-see-what-your-agent-instruction-files-cost/6af2d0a15d456961fae8fe32/comment/6af318ab8d0998379daa40ba#reply-6af379592bc9340ddaa892a9)

Thanks Mo! Keeping the always-loaded file to a short index and reading notes on demand is exactly the kind of split Clogmeter helps you spot. Glad it's a problem worth measuring.
