useclis.
Saved CLIs

Submit your CLI

Free to list

Put your command-line tool in the hands of agents.

Link to the public repository where your CLI lives.

A CLI that agents can use.

Include a working command, public documentation, and a clear task an agent can accomplish with your tool.

2. The essentials

A concrete use case helps people find the right tool.

Directory listing

A CLI profile with your repository, documentation, and command. Submissions are reviewed before appearing in the directory.

Free

Submissions are public GitHub issues.

Sign in to GitHub, then review and create your issue.

Gitleaks

gitleaksTesting & qualityBy gitleaks ↗

Scan source code and Git history for potential leaked credentials.

For your agent

Add a command-line secret scan to an agent’s code-review workflow.

Agent/AI workflow support: Not marked in source list (source list)

Example command

gitleaks --help

Run after following the project’s setup instructions. Local files, credentials, or a connected service may be required.

What it does

  • Secret scanning
  • Git history scanning
  • Scan reports

Homebrew installs

gitleaks ↗

Explicitly requested installation events

30 days
10,826
90 days
36,400
365 days
114,249

From Homebrew installations that report analytics. Includes package variants; counts are not unique users.

Checked . Source dated . How installs are counted ↗

Repository activity

Commits per week · GitHub snapshot

6 commits over 12 weeks
01211 weeks before snapshotLatest week

Tap, hover, or use the arrow keys to inspect weekly commits. The latest week may be incomplete.

Commands and capabilities are described from the project documentation. Repository statistics cover gitleaks/gitleaks, which may contain more than the CLI. Listing a tool does not mean every command has been tested with every agent.