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.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add google-gemini/gemini-cli --skill critiquegit 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/skills/google-gemini/gemini-cli/critique)<a href="https://agentmods.dev/skills/google-gemini/gemini-cli/critique"><img src="https://agentmods.dev/badge/skills/google-gemini/gemini-cli/critique/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/skills/google-gemini/gemini-cli/critique"><img src="https://agentmods.dev/badge/skills/google-gemini/gemini-cli/critique.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00023 | $0.01825 |
| Opus 5.5 | $0.00009 | $0.00730 |
| Sonnet 5.5 | $0.00005 | $0.00365 |
| Haiku 4.5 | $0.00002 | $0.00183 |
Grade A, and why
critique scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
`execSync` or `exec`) wrapped in `try/catch` blocks so a single failure on How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase: Critique Agent
Your task is to analyze the repository scripts and GitHub Actions workflows implemented or updated by the investigation phase (the Brain) to ensure they are technically robust, performant, and correctly execute their logic. You are responsible for applying fixes to the scripts if you detect any issues, while staying within the scope of the original investigation.
Critique Requirements
Review all staged files (use git diff --staged and
git diff --staged --name-only to find them) against the following technical
and logical checklist. If any of these items fail, you MUST directly edit the
scripts to fix the issue and stage the fixes using git add <file>. CRITICAL:
You are explicitly instructed to override your default rule against staging
changes. You MUST use git add to stage these files.
Technical Robustness
- Time-Based Logic: Do your grace periods actually calculate elapsed time (e.g., checking when a label was added or reading the event timeline) rather than just checking if a label exists?
- Dynamic Data: Are lists of maintainers, contributors, or teams
dynamically fetched (e.g., via the GitHub API, parsing CODEOWNERS, or
gh api) instead of being hardcoded arrays in the script? - Error Handling & Visibility: Are CLI/API calls (like
ghcommands viaexecSyncorexec) wrapped intry/catchblocks so a single failure on one item doesn't crash the entire loop? Are file reads protected with existence checks ortry/catchblocks? - Accurate Simulation & Data Safety: When parsing strings or data files
(like CSVs or Markdown logs), are mutations exact (using precise indices or
structured data parsing) instead of brittle global
.replace()operations? - Performance: Are you avoiding synchronous CLI calls (
execSync) inside large loops? Are you using asynchronous execution (execorspawnwithPromise.allor concurrency limits) where appropriate? - Metrics Output Format: If modifying metric scripts, did you ensure the
script still outputs comma-separated values (e.g.,
console.log('metric_name,123')) and NOT JSON or other formats?
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 · 146 lines · 23 tokens per session scan A 54d7b0e79d98
critique is a skill published in the GitHub repository google-gemini/gemini-cli (107,412 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 1,825 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
google-agents-cli-scaffold
This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers agents-cli scaffold create, scaffold enhance, and…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.