A curated directory of product CLIs, developer tools, and terminal apps — verified for humans, scripts, and AI agents.
>_$ snyk
Scan source code, dependencies, containers, and infrastructure as code for security vulnerabilities.
>_$ bw
Access and manage Bitwarden vault items, organizations, collections, and secrets from scripts.
>_$ doppler
Fetch and inject Doppler secrets into local commands, applications, and deployment workflows.
>_$ infisical
Authenticate, inject secrets, export configuration, and scan repositories for leaked credentials.
>_$ ggshield
Detect exposed secrets in repositories, commits, files, Docker images, and CI pipelines.
>_$ trivy
Scan containers, filesystems, repositories, Kubernetes, and SBOMs for vulnerabilities and misconfiguration.
>_$ vault
Read, write, rotate, and manage secrets, authentication methods, policies, and encryption services.
>_$ tailscale
Connect devices to a tailnet, inspect peers, serve local apps, create funnels, and manage networking.
>_$ gitleaks
Detect hardcoded secrets in Git repositories, files, and CI pipelines.
>_$ semgrep
Find security and correctness issues with fast semantic code analysis.
>_$ sops
Encrypt structured configuration files using cloud KMS, age, or PGP.
>_$ age
Simple, modern, and secure file encryption with small explicit keys.
>_$ nmap
Discover hosts, services, ports, and network configurations.
Common questions about CLI tools, Agent CLIs, and command line automation
A CLI, or command-line interface, lets you control software by typing commands in a terminal instead of clicking through a graphical interface. CLI tools are useful for development, automation, scripts, CI pipelines, and repeatable operations.
An Agent CLI is either a command-line tool for operating an AI agent or a conventional CLI designed to be called reliably by AI agents. Agent-friendly CLIs expose clear commands, non-interactive options, predictable output, and meaningful exit codes so an agent can plan, execute, and verify work.
Yes. AI coding agents can invoke many of these CLIs through a shell to work with repositories, cloud services, databases, productivity apps, and deployment systems. Tools marked Agent-ready are especially suitable for scripted or autonomous use, but authentication and permissions still need to be configured safely.
The best CLI tools for AI agents support non-interactive commands, stable flags, structured or parseable output, standard input and output, documented authentication, and reliable exit codes. These features make results easier for an agent to interpret and verify without manual intervention.
Choose an official CLI when you need first-party support, close alignment with a service API, and predictable updates. A community CLI can be a better fit when it offers a simpler workflow or capabilities the official tool lacks. Review its repository, maintenance activity, permissions, and installation instructions before use.
