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/core.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/core)<a href="https://agentmods.dev/commands/google-gemini/gemini-cli/core"><img src="https://agentmods.dev/badge/commands/google-gemini/gemini-cli/core/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/core"><img src="https://agentmods.dev/badge/commands/google-gemini/gemini-cli/core.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.00343 |
| Opus 5.5 | $0.00000 | $0.00137 |
| Sonnet 5.5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
core 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.
What it actually says
description="Injects context of all relevant cli files" prompt = """ The following output contains the complete source code of packages/core. Pay extremely close attention to these files. They define the project's core architecture, component patterns, and testing standards.
The source code contains the content of absolutely every source code file in packages/core. You should very rarely need to read any other files from packages/core to resolve prompts.
!{find packages/core \( -path packages/cli/dist -o -path packages/core/dist -o -name node_modules \) -prune -o -type f \( -name ".ts" -o -name ".tsx" \) ! -name ".test.ts" ! -name ".test.tsx" ! -name "*.d.ts" -exec echo "--- {} ---" \; -exec cat {} \;}
In addition to the code context, you MUST strictly adhere to the following frontend-specific development guidelines when writing code in packages/core.
Configuration & Settings
- Settings vs Args: Use settings for user-configurable options; do not add new CLI arguments.
- Schema: Add new settings to
packages/cli/src/config/settingsSchema.ts. - Documentation:
- If
showInDialog: true, document indocs/get-started/configuration.md. - Ensure
requiresRestartis correctly set.
- If
General
- Logging: Use
debugLoggerfor errors. NEVER leaveconsole.log/warn/errorin the code. - TypeScript: Avoid the non-null assertion operator (
!).
{{args}}. """
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 · 30 lines · 0 tokens per session scan A 7d0f430eae75
core 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 343 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.