Skip to content

We use analytics cookies to see how the site is used. They are only set if you accept. Accepting also turns on session recording (pages viewed, clicks and scrolls) so we can fix problems; what you type stays hidden. It also lets Meta (Facebook) see your visit, so we can measure our ads. Read the privacy policy

A drill core cut into layers labelled badges, pitch and first command, with a depth scale marked in words.

README Examples From 30 Popular CLI Repos: How Many Words Come Before the First Command

We pulled the README of the 30 most-starred GitHub repositories tagged cli and measured what sits above the first command a visitor can paste: prose, badges and pictures.

Core from a median README, top to bottom.

Where we drilled

On 12 November 2026 we took the 30 most-starred GitHub repositories carrying the topic cli, as returned by the repository search API sorted by stars, and downloaded each default README through the README endpoint. Then we measured every file the same way, with a script, and checked the edge cases by hand.

The question was narrow on purpose. A visitor who wants to try a tool is looking for one thing: a line to paste into a terminal. So for each README we counted the words of prose that come before the first command a reader can copy to install or run the project. We also counted badges, pictures, total length and whether there is an Install heading.

  • A word is any run of characters with a letter or digit, outside code blocks, HTML tags and image markup. Link text counts, link addresses do not.
  • A command is a package manager or install line (brew install, npm i, pipx install, cargo install, curl ... | sh and the like) or a zero-install run line, inside a code block, inline code or a table cell.
  • A badge is an image from a badge service or a CI status image.

How deep the first command sits, repo by repo

25 of the 30 READMEs contain a command a visitor can paste. Across those 25, the median depth is 261 words: roughly one screen of reading on a laptop before the first line you can run. Six put it under 150 words. The deepest, sharkdp/fd, puts it after 2,466 words, below a long feature tour and benchmark section.

  1. codewhale-hq/Codewhale44
  2. sherlock-project/sherlock46
  3. google/zx60
  4. wagoodman/dive64
  5. obsidianmd/obsidian-skills77
  6. ajeetdsouza/zoxide133
  7. n8n-io/n8n169
  8. tldr-pages/tldr195
  9. Raphire/Win11Debloat202
  10. rtk-ai/rtk207
  11. herdrdev/herdr207
  12. Aider-AI/aider241
  13. google-gemini/gemini-cli261
  14. junegunn/fzf272
  15. morluto/rea305
  16. ohmyzsh/ohmyzsh325
  17. chubin/cheat.sh334
  18. spf13/cobra413
  19. OpenHands/OpenHands428
  20. tw93/Pake459
  21. sharkdp/bat816
  22. yt-dlp/yt-dlp822
  23. jesseduffield/lazygit1,442
  24. BurntSushi/ripgrep1,447
  25. sharkdp/fd2,466
Words of prose above the first pasteable command, shallowest first. Bar length is relative to the deepest file (2,466 words). Measured 12 November 2026.

The shallow end is mostly newer, single-purpose tools: codewhale-hq/Codewhale (44 words, then curl -fsSL ... | sh), sherlock-project/sherlock (46 words, a pipx install line in a table) and google/zx (60 words, then npm install zx). The deep end is older tools with long READMEs: BurntSushi/ripgrep and jesseduffield/lazygit both pass 1,400 words before their install section.

What the layers above the command hold

  • 30 of 30repositories fill in the one-line description in the About box, so a visitor reads a pitch before the README starts.
  • 4badges is the median. Seven READMEs carry none at all; yt-dlp/yt-dlp carries the most, 13.
  • 28 of 30show at least one picture that is not a badge: a logo, a screenshot or a demo. Six embed an animated GIF, a video or a terminal recording we could identify by file type.
  • 19 of 30have a heading with the word Install in it. 21 have a Quick start, Getting started, Usage or Example heading.
  • 1,136words is the median length of the whole README. The shortest, google/zx, has 125; the longest, yt-dlp/yt-dlp, has 16,549 because it carries the full option reference.

The spread matters more than the medians. A 125-word README and a 16,549-word README both sit in the top 30. Length alone does not decide whether a project gets used; what a reader meets first is the part every one of them works on.

Five READMEs with no shell command at all

Five files never give a line to paste into a terminal. Each one sends the visitor somewhere else instead, and the choice is deliberate in every case:

  • cli/cli links to an installation section and to separate docs for each platform.
  • sxyazi/yazi links to its documentation site for installation and usage.
  • jeecgboot/JeecgBoot, written in Chinese, links to a one-click install page on its help site.
  • Panniantong/Agent-Reach, also in Chinese, gives a sentence to paste into an AI coding agent, which then reads an install file from the repository.
  • charmbracelet/bubbletea is a Go library, so its README opens a tutorial with code to import rather than a tool to install.

Pointing to docs keeps one source of truth for many platforms. The cost is one more click for a visitor who only wanted to try it.

The full core box: all 30 READMEs

Stars, length and depth as read on 12 November 2026. Stars change daily; the README files can change on any commit.

RepositoryStarsREADME wordsWords before first commandBadges
morluto/rea454,4312,7293059
n8n-io/n8n210,2904381690
yt-dlp/yt-dlp207,18516,54982213
ohmyzsh/ohmyzsh190,5822,5053256
Panniantong/Agent-Reach111,264365none8
sherlock-project/sherlock110,462151461
google-gemini/gemini-cli108,7969522616
OpenHands/OpenHands93,3221,4424284
rtk-ai/rtk86,3381,8852078
junegunn/fzf84,1762,9712728
jesseduffield/lazygit83,8712,3901,4426
BurntSushi/ripgrep69,9122,3581,4473
tldr-pages/tldr64,1977471950
tw93/Pake63,4277244595
Raphire/Win11Debloat62,4461,1142023
sharkdp/bat61,2383,7618164
wagoodman/dive54,7231,157645
obsidianmd/obsidian-skills51,862324770
herdrdev/herdr50,5313292076
Aider-AI/aider50,0878152415
jeecgboot/JeecgBoot48,442777none8
cli/cli46,984518none0
google/zx45,844125600
charmbracelet/bubbletea45,7161,275none2
sharkdp/fd45,0553,1002,4663
spf13/cobra44,7895054134
sxyazi/yazi43,383462none0
chubin/cheat.sh41,8572,82633412
codewhale-hq/Codewhale41,1781,764444
ajeetdsouza/zoxide40,5781,3381330

What this sample cannot tell you

It shows what popular READMEs do, not what makes a visitor become a user. Nobody outside these projects can see how many readers scrolled, copied a command or installed. Stars also build up over years, so a README rewritten last month gets credit for stars earned by an older version.

The sample is one topic and one moment: 30 repositories tagged cli, read on one day. Libraries, apps and frameworks may look different. Use the numbers as a reference point when you edit your own file, and check them against GitHub's own advice on READMEs, which lists what a README usually answers: what the project does, why it is useful, how to start, where to get help and who maintains it.

If your first command sits deeper than about 260 words, you are deeper than half of this sample. Moving one install line up is the cheapest edit you can make.