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/review-frontend.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/review-frontend)<a href="https://agentmods.dev/commands/google-gemini/gemini-cli/review-frontend"><img src="https://agentmods.dev/badge/commands/google-gemini/gemini-cli/review-frontend/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/review-frontend"><img src="https://agentmods.dev/badge/commands/google-gemini/gemini-cli/review-frontend.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.00368 |
| Opus 5.5 | $0.00000 | $0.00147 |
| Sonnet 5.5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
review-frontend 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- review-frontend — 100% identical, 0 lines differ
What it actually says
description="Reviews a pull request based on issue number." prompt = """ Please provide a detailed pull request review on GitHub issue: {{args}}.
Follow these steps:
- Use
gh pr view {{args}}to pull the information of the PR. - Use
gh pr diff {{args}}to view the diff of the PR. - Understand the intent of the PR using the PR description.
- If PR description is not detailed enough to understand the intent of the PR, make sure to note it in your review.
- Make sure the PR title follows Conventional Commits, here are the last five commits to the repo as examples: !{git log --pretty=format:"%s" -n 5}
- Search the codebase if required.
- Write a concise review of the PR, keeping in mind to encourage strong code quality and best practices. Pay particular attention to the Gemini MD file in the repo.
- Consider ways the code may not be consistent with existing code in the repo. In particular it is critical that the react code uses patterns consistent with existing code in the repo.
- Follow these detailed review rules: !{cat .gemini/commands/strict-development-rules.md}
- Discuss with me before making any comments on the issue. I will clarify which possible issues you identified are problems, which ones you need to investigate further, and which ones I do not care about.
- If I request you to add comments to the issue, use
gh pr comment {{args}} --body {{review}}to post the review to the PR.
Remember to use the GitHub CLI (gh) with the Shell tool for all
GitHub-related tasks.
"""
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 · 32 lines · 0 tokens per session scan A caf58d4170ad
review-frontend 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 368 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
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
afrv
Revise the current feature worktree after code review — decide accept/revert/modify (shortcut for feature-code-revise).
implement-revalidate
Read by /implement when the user asks to re-validate (D-CMD-REF-HAND).
align
Context-aware alignment. In plan mode it audits the active plan and folds the amendments in. Otherwise it reviews the branch, a named branch, or a pull request against Ion's principles, authors a fix plan, and after approval implements and commits the fixes.
request-review-plan
Request Code Review Phases 1-2: Planning scope and assembling reviewer context.
eg-precommit-review
Run the pre-commit independent-reviewer loop on the current branch's pending changes.