PowerShell by the Numbers
Original research from the PowerShell Genie reference: what 182 documented commands, 111 real-world scripts, and 83 lessons reveal about how PowerShell is actually used.
Method: every number below was computed from this site's own published reference on 25 October 2026. Command counts come from the 182 command pages in our reference; verb and module groupings come from the cmdlet names themselves. No surveys, no estimates.
The headline numbers
- 182 commands documented in the reference
- 46 distinct approved verbs in use
- 84 Get-* commands — 46% of the whole reference
- 98 commands (54%) only read, inspect, or report — they change nothing
- 111 real-world admin scripts in the script library
- 83 beginner lessons, 13 in-depth guides
Nearly half of PowerShell just reads things
The single most useful fact for a beginner: 84 of 182 commands start with Get-. Another 14 only inspect, test, or format output (Test-, Resolve-, Measure-, Search-, Find-, Compare-, Select-, Format-, Out-). Together, 98 commands — 54% — cannot change anything on your system. That is why experienced admins explore fearlessly: run the Get- commands first, understand the objects, and only then reach for Set-, New-, or Remove-.
Verb distribution
| Verb | Commands | What it means |
|---|---|---|
| Get- | 84 | Retrieve data — the workhorse verb |
| Set- | 12 | Change a setting or property |
| Remove- | 8 | Delete something |
| Start- / Stop- | 7 / 5 | Control processes, services, jobs |
| New- | 7 | Create something |
| Write- | 6 | Send output |
| All other verbs (36 verbs) | 53 | One to three commands each |
Takeaway: learn Get- first and you can read more than half the language. Learn Set-, New-, and Remove- next and you can change almost everything else.
Where the commands live: module families
| Family | Commands | Share |
|---|---|---|
| Core PowerShell (built-in cmdlets) | 136 | 75% |
| Active Directory | 25 | 14% |
| Azure (Az module) | 11 | 6% |
| Microsoft Graph / Entra ID | 9 | 5% |
| Exchange Online | 1 | 1% |
Active Directory is the largest single admin domain in the reference (25 commands) — ahead of Azure and Graph combined. That matches the day-to-day reality of Windows infrastructure work: identity and directory tasks dominate admin scripting.
Most-covered nouns
The nouns that appear most often show what admins actually manage with PowerShell: objects (8 commands), modules (6), services, jobs, and items (5 each), then scheduled tasks, sessions, processes, paths, and content (4 each). If you master objects and the pipeline, the rest of the language follows.
Scripts vs commands
The reference documents 182 individual commands, but the script library holds 111 complete, task-sized scripts — audits, bulk user jobs, replication checks, offboarding workflows. The ratio matters: real admin work is rarely one command. It is a pipeline of several, wrapped in a script with error handling. That is why every command page on this site links toward scripts and exercises, not just syntax.
Cite this research
If you quote these numbers, link to this page so readers can check the method:
<a href="https://powershellgenie.com/powershell-by-the-numbers/">PowerShell by the Numbers — PowerShell Genie</a>
See also: PowerShell cheat sheet, Command finder, Command reference.
Genie guide
Install only what the task needs. Each module page covers setup and the commands you will actually use.
How PowerShell is actually used, measured from 182 documented commands.
Reading 1 of 7 sections
Error decoder
Paste the red text. The decoder names the kind of error it is and points at the lesson that fixes it. It never runs your code, and decoding happens entirely in your browser — your pasted error is never sent anywhere.