• There are 16 files with 3,810 lines of code.
• 1 very long files (1,034 lines of code)
• 1 long files (817 lines of code)
• 3 medium size files (1,097 lines of code)
• 3 small files (469 lines of code)
• 8 very small files (393 lines of code)

File	# lines	≈ tokens to read	# changes (1y)	≈ lines edited per change	lines read per line changed
_blueprint.py in chz/blueprint	1034	~7k–15k	1	~300	~3
tiepin.py in chz	817	~5k–15k	1	~150	~5
data_model.py in chz	484	~3k–7k	1	~100	~3
factories.py in chz	399	~2k–7k	1	~100	~3
_argmap.py in chz/blueprint	214	~1k–3k	1	~70	~3
validators.py in chz	165	~1k–3k	1	~50	~3
_entrypoint.py in chz/blueprint	108	~700–2k	1	~50	~2
_lazy.py in chz/blueprint	99	~500–1.5k	1	~30	~3
_argv.py in chz/blueprint	88	~500–1.5k	1	~50	~2
_wildcard.py in chz/blueprint	74	~500–1.5k	1	~50	~2
__init__.py in chz	62	~300–1k	1	~20	~3
__init__.py in chz/blueprint	17	under 1k	1	~5	~3

Tokens are lines × 7 to 14 (analysis.fileReadsForChanges). Lines edited per change are the file's lines added and deleted divided by its commits over the whole history. Agents read about 2,000 lines at a time: when a 17,000-line file was split into modules, the tokens an agent read for the same change fell by 83% (The Economic Benefit of Refactoring, 2026).

There are 3 files with lines longer than 120 characters. In total, there are 5 long lines.

File	# lines	# units	# long lines
tiepin.py in chz	817	21	2
_blueprint.py in chz/blueprint	1034	41	2
factories.py in chz	399	31	1

• File size measurements show the distribution of size of files.
• Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
• It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.