Discover command-line AI tools and terminal utilities for developers.
CLI Tools tools are AI-powered software designed to help developers and teams tackle cli tools-related tasks more efficiently. These tools are typically published as open-source projects on GitHub and can be integrated into existing workflows via MCP (Model Context Protocol), Claude Skills, or standalone agent frameworks. On Agent Skills Hub, we index 10 quality-scored cli tools tools across languages including Awk, Rust, TypeScript.
In 2026, the AI agent ecosystem is maturing rapidly. CLI Tools tools can significantly boost development efficiency by automating repetitive tasks, reducing human error, and providing intelligent suggestions. The top 3 tools — x-cmd, shell-use, cchistory — have earned an average of 6,672 GitHub stars, reflecting strong community validation. 10 of the listed tools come with clear open-source licenses, ensuring freedom to use and modify.
When choosing a cli tools tool, consider these factors: 1) Community activity — GitHub stars and recent commit frequency indicate reliability; 2) Integration method — check if it supports MCP, Claude, or your preferred agent framework; 3) Language compatibility — the most common language in this list is Awk; 4) Quality score — Agent Skills Hub's composite score evaluates code quality, documentation completeness, and maintenance activity. Our recommendation: start with x-cmd — it ranks highest in both star count and quality score.
Best Buddy for AI Agents. Bootstrap 1000+ command line tools in seconds.
💻 Make the terminal / shell accessible for AI agents. Automate tasks with ease.
```sh
brew tap microsoft/shell-use https://github.com/microsoft/shell-use
brew install shell-use
```Like the shell history command but for your Claude Code sessions.
🐹 Clean, uninstall, analyze, optimize, and monitor your Mac from the terminal.
An intelligent CLI tool that intercepts terminal errors and provides instant, context-aware solutions using LLM's. Transform natural language into terminal commands and never get stuck on cryptic error messages again! Currently in early development.
CLI tool that uses Codex to turn natural language commands into their Bash/ZShell/PowerShell equivalents
A universal CLI client for MCP. mcpc supports persistent sessions, stdio/HTTP, OAuth 2.1, tasks, JSON output for code mode, proxy for AI sandboxes, x402, and more.
Fast, stateless LLM for your shell: qq answers; qa runs commands
Custom status line for Claude Code showing model, tokens, rate limits, and git info in real-time
mcpc is a CLI client for MCP. It supports persistent sessions, stdio/HTTP, OAuth 2.1, JSON output for code mode, proxy for AI sandboxes, and much more.
| Tool | Stars | Language | License | Score |
|---|---|---|---|---|
| x-cmd | ★ 4.2k | Awk | Apache-2.0 | 43 |
| shell-use | ★ 188 | Rust | MIT | 53 |
| cchistory | ★ 127 | TypeScript | MIT | 40 |
| Mole | ★ 57.5k | Shell | GPL-3.0 | 52 |
| Shellsage | ★ 77 | Python | Apache-2.0 | 31 |
| Codex-CLI | ★ 2.3k | Python | MIT | 35 |
| mcpc | ★ 694 | TypeScript | Apache-2.0 | 51 |
| qqqa | ★ 621 | Rust | MIT | 45 |
| ClaudeCodeStatusLine | ★ 499 | Shell | MIT | 45 |
| mcp-cli | ★ 459 | TypeScript | Apache-2.0 | 47 |
The top cli tools in 2026 are x-cmd, shell-use, cchistory. Agent Skills Hub ranks 10 options by GitHub stars, quality score (6 dimensions including completeness, examples, and agent readiness), and recent activity. The list is rebuilt every 8 hours from live GitHub data.
x-cmd (4.2k stars) is the most adopted choice for general cli tools workflows, written in Awk. shell-use (188 stars) is a strong alternative and uses Rust instead. Pick by your existing stack: match the language and runtime your team already uses to minimize integration cost. If unsure, start with x-cmd — it has the deepest community and the most examples online.
Avoid pre-built cli tools when (1) your use case requires deep customization that the tool's plugin system doesn't support, (2) you have strict compliance requirements that ban third-party dependencies, (3) the tool's maintenance is inactive (last commit >6 months ago), or (4) your data volume is small enough that a 50-line custom script is cheaper than learning the tool. For most production workflows above 100 requests/day, the time savings from a maintained tool outweigh the customization loss.
CLI Tools focuses specifically on discover command-line ai tools and terminal utilities for developers. Workflow Automation is a related but distinct category — see https://agentskillshub.top/best/workflow-automation/ for those tools. The two often appear in the same agent pipeline but solve different problems: choose cli tools when your primary goal is the specific task, and workflow automation when the workflow is broader.
For most teams, yes. x-cmd has 4.2k stars worth of community testing, handles edge cases you haven't thought of, and ships with documentation. Build your own only when (1) your requirements are deeply non-standard, (2) you have a security/compliance reason to avoid OSS dependencies, or (3) the maintenance burden is small enough (<200 lines of code) that you'll save time long-term. The break-even point is usually around 2-3 weeks of dev time saved.
Most cli tools listed are open source under permissive licenses (MIT, Apache 2.0). A handful offer paid managed/cloud versions on top of free self-hosted core. Always check the LICENSE file on each tool's GitHub repository before commercial use — some use AGPL or non-commercial restrictions that may not fit your deployment model.