• There are 8 files with 8,077 lines of code.
• 3 very long files (6,361 lines of code)
• 2 long files (1,221 lines of code)
• 2 medium size files (456 lines of code)
• 0 small files (0 lines of code)
• 1 very small files (39 lines of code)

File	# lines	≈ tokens to read	# changes (1y)	≈ lines edited per change	lines read per line changed
registry.yaml in root	3530	~20k–50k	107	~15	~300
authors.yaml in root	548	~3k–10k	39	~5	~100
build-your-own-fact-checker-cerebras.ipynb in articles/gpt-oss	1635	~10k–30k	2	~700	~2

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 7 files with lines longer than 120 characters. In total, there are 321 long lines.

File	# lines	# units	# long lines
build-your-own-fact-checker-cerebras.ipynb in articles/gpt-oss	1635	-	187
fine-tune-transfomers.ipynb in articles/gpt-oss	673	-	52
registry.yaml in root	3530	-	29
fine-tune-korean.ipynb in articles/gpt-oss	1196	-	21
run-nvidia.ipynb in articles/gpt-oss	209	-	14
authors.yaml in root	548	-	10
run-colab.ipynb in articles/gpt-oss	247	-	8

• 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.