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 prsgit 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/prs)<a href="https://agentmods.dev/skills/google-gemini/gemini-cli/prs"><img src="https://agentmods.dev/badge/skills/google-gemini/gemini-cli/prs/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/prs"><img src="https://agentmods.dev/badge/skills/google-gemini/gemini-cli/prs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- 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.00027 | $0.00583 |
| Opus 5.5 | $0.00011 | $0.00233 |
| Sonnet 5.5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
prs 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: GitHub PR & Git Management
Goal
Standardize how the Gemini CLI Bot stages its changes, generates Pull Request descriptions, and manages the lifecycle of both new and existing PRs.
Staging & Patch Preparation (MANDATORY)
If you are proposing fixes and PR creation is enabled (per the System Directive):
- Surgical Changes: Only propose a single improvement or fix per PR.
- No Bundling: You are STRICTLY FORBIDDEN from bundling unrelated changes. Changes are unrelated if they address different root causes.
- Examples: Do not combine a script fix with a documentation update, an unrelated refactor, or a metrics script update. Metrics and fixes MUST be in separate PRs.
- Generate PR Description: Use the
write_filetool to createpr-description.md.- Title: The very first line MUST be a concise, conventional title.
- Body: The rest should be the markdown body explaining the change, why it is recommended, and the expected impact.
- Stage Fixes: You MUST explicitly stage your fixes using the
git add <files>command. - Internal File Protection (CRITICAL): You are STRICTLY FORBIDDEN from
staging internal bot management files. If they are accidentally staged, you
MUST unstage them using
git reset <file>.- NEVER STAGE:
pr-description.md,lessons-learned.md,branch-name.txt,pr-comment.md,pr-number.txt,issue-comment.md, or anything inhistory/.
- NEVER STAGE:
Unblocking & PR Updates (Recovery)
If you are continuing work on an existing Task or responding to a comment on an existing bot PR:
- Target Existing Branch: Use
write_fileto generatebranch-name.txtcontaining the current branch name (e.g.,bot/task-BT-01). - Track PR ID: Use
write_fileto generatepr-number.txtcontaining the numeric PR ID. - Respond to Maintainers:
- For general responses, write your markdown comment to
issue-comment.md. - For specific PR feedback, write your markdown response to
pr-comment.md.
- For general responses, write your markdown comment to
- Handle CI Failures: Diagnose failing checks using
gh run view. Your priority must be generating a new patch and staging it withgit addto fix the failure.
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 · 52 lines · 27 tokens per session scan A dace221f16d4
prs is a skill published in the GitHub repository google-gemini/gemini-cli (107,434 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 583 once invoked, about $0.0001 per session on Opus 5.5. 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-08-30.
Other skills, from other repositories
ccmanager-config
Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global /.config/ccmanager/config.json. Use when someone wants ccmanager to launch a different agent CLI (codex, gemini, cursor-agent, copilot…), add command presets, run a command on session state changes or worktree…
ccb-github
Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README/zh.md, localized README files, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state…
maestro-fork
Create or sync session worktree for parallel dev.
maestro-merge
Merge session worktree branch back to main.
cli-collaboration
Use when multiple CLI agents or assistants alternate on the same repository or explicit shared handoff workflow — especially with AGENTHANDOFF.md, side-by-side AGENTS.md/CLAUDE.md/GEMINI.md, dirty worktrees, ownership notes, red tests, resume/continue requests, or /cli-collaboration in Grok Build.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.