• There are 6 files with 1,562 lines of code.
• 0 very long files (0 lines of code)
• 1 long files (611 lines of code)
• 2 medium size files (774 lines of code)
• 1 small files (135 lines of code)
• 2 very small files (42 lines of code)

File	# lines	≈ tokens to read	# changes (1y)	≈ lines edited per change	lines read per line changed
Parser.scala in src/main/scala/pa	611	~3k–10k	4	~30	~20
model.scala in src/main/scala/pa	443	~3k–7k	5	~20	~20
PaClient.scala in src/main/scala/pa	135	~700–2k	2	~20	~7

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

File	# lines	# units	# long lines
PaClient.scala in src/main/scala/pa	135	22	38
Parser.scala in src/main/scala/pa	611	25	3

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