• There are 50 files with 8,682 lines of code.
• 1 very long files (1,151 lines of code)
• 1 long files (921 lines of code)
• 13 medium size files (4,037 lines of code)
• 9 small files (1,282 lines of code)
• 26 very small files (1,291 lines of code)

File	# lines	≈ tokens to read	# changes (1y)	≈ lines edited per change	lines read per line changed
s3.go in storage	1151	~7k–20k	2	~30	~30
stat.go in command	201	~1k–3k	4	~150	~2
app.go in command	253	~1.5k–5k	3	~15	~20
token_manager.go in storage	322	~2k–5k	2	~100	~3
main.go in root	21	under 1k	2	~50	~0

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

File	# lines	# units	# long lines
cp.go in command	921	24	14
pipe.go in command	285	8	8
s3.go in storage	1151	42	4
sync.go in command	453	10	4
auto_complete.go in command	183	8	4
app.go in command	253	4	4
select.go in command	365	6	4
progressbar.go in progressbar	58	13	1
.goreleaser.yml in root	53	-	1
context.go in command	85	3	1
wildcard.go in command	51	3	1
validation.go in command	55	4	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.