Gemini CLI is a terminal-based AI agent that lets developers interact with Google Gemini models and use tools for tasks such as file operations, shell commands, web fetching, and search. Developers use it from the command line, and the catalogue add-ons extend its workflows and integrations.
Borrowing it
Nothing to install: this file belongs to google-gemini/gemini-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/google-gemini/gemini-cli/main/.gemini/commands/find-docs.tomlgit clone --depth 1 https://github.com/google-gemini/gemini-cliWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/google-gemini/gemini-cli/find-docs)<a href="https://agentmods.dev/commands/google-gemini/gemini-cli/find-docs"><img src="https://agentmods.dev/badge/commands/google-gemini/gemini-cli/find-docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/google-gemini/gemini-cli/find-docs"><img src="https://agentmods.dev/badge/commands/google-gemini/gemini-cli/find-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00469 |
| Opus 5.5 | $0.00000 | $0.00188 |
| Sonnet 5.5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
find-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description = "Find relevant documentation and output GitHub URLs."
prompt = """
Mission: Find Relevant Documentation
Your task is to find documentation files relevant to the user's question within the current git repository and provide a list of GitHub URLs to view them.
Workflow:
-
Identify Repository Details:
- You may use shell commands like
gitorghto get the remote URL of the repository. - From the remote URL, parse and construct the base GitHub URL (e.g.,
https://github.com/user/repo). You must handle both HTTPS (https://github.com/user/repo.git) and SSH ([email protected]:user/repo.git) formats. - Determine the default branch name. You can assume
mainfor this purpose, as it is the most common.
- You may use shell commands like
-
Search for Documentation:
- First, perform a targeted search across the repository for documentation files (e.g.,
.md,.mdx) that seem directly related to the user's question. - If this initial search yields no relevant results, and a
docs/directory exists, read the content of all files within thedocs/directory to find relevant information. - If you still can't find a direct match, broaden your search to include related concepts and synonyms of the keywords in the user's question.
- For each file you identify as potentially relevant, read its content to confirm it addresses the user's query.
- First, perform a targeted search across the repository for documentation files (e.g.,
-
Construct and Output URLs:
- For each file you identify as relevant, construct the full GitHub URL by combining the base URL, branch, and file path. Do not use shell commands for this step.
- The URL format should be:
{BASE_GITHUB_URL}/blob/{BRANCH_NAME}/{PATH_TO_FILE_FROM_REPO_ROOT}. - Present the final list to the user as a markdown list. Each item in the list should be the URL to the document, followed by a short summary of its content.
- If, after all search attempts, you cannot find any relevant documentation, ask the user clarifying questions to better understand their needs. Do not return any URLs in this case.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 31 lines · 0 tokens per session scan A 0dfe6c957646
find-docs is a command published in the GitHub repository google-gemini/gemini-cli (107,525 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 469 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-02.
Other commands, from other repositories
maestro-odyssey
Long-running iterative cycle — one entry, seven modes (debug|improve|planex|review|security|defensive|ui). Shared archaeology/audit → fix → verify → generalize → discover → persist skeleton with mode-specific dimensions. User-invoked campaign entry; single-step fixes route via /maestro-next.
maestro-overlay
Create or edit command overlays from natural language, or auto-generate them from workflow deficiency signals.
dispatch
Every task description uses structured format for clarity.
maestro-session-manage
Manage a v3 Session — inspect status/resume-view, review knowledge candidates, complete, archive/unarchive.
maestro-knowledge
Intent-driven knowledge-store and Run knowledge lifecycle management — read-only audit/prune reports, stage candidates (with signal recording), review/resolve/promote candidates, harvest artifacts, or manage wiki/domain knowledge.
monitor
Command "monitor" from catlog22/maestro-flow, covering monitor pipeline, constants, handler router, handlecallback and handlecheck.