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 agentmods add skills/fprochazka/claude-code-plugins/gemini-clinpx skills add fprochazka/claude-code-plugins --skill gemini-cligit clone --depth 1 https://github.com/fprochazka/claude-code-pluginsWhat 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 | $0.00121 | $0.01137 |
| Opus 5 | $0.00060 | $0.00568 |
| Sonnet 5 | $0.00024 | $0.00227 |
| Haiku 4.5 | $0.00012 | $0.00114 |
Grade A, and why
gemini-cli 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 2d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemini CLI Integration
Always run through subagents for better iteration and summarization. Make the subagent always ask Gemini to provide evidence, and make the subagent verify the findings before summarizing for the main agent.
NEVER use --approval-mode yolo or --yolo. Gemini must not auto-approve destructive actions.
Quick Reference
# Basic one-shot query (non-interactive mode)
gemini "Explain this codebase architecture"
# Specify model (by alias or full ID)
gemini -m flash "Standard analysis task"
gemini -m pro "Deep reasoning task"
gemini -m gemini-2.5-flash "Use specific GA model"
# Include additional directories in context
gemini --include-directories ./libs,./shared "Analyze dependencies"
# Multi-line prompt using heredoc
gemini <<'__GEMINI_PROMPT__'
Analyze this codebase for security vulnerabilities.
Focus on: SQL injection, XSS, authentication issues
__GEMINI_PROMPT__
# Output formats
gemini -o json "query" # structured JSON output
gemini -o text "query" # default
gemini -o stream-json "query" # real-time JSONL events
Available Models
Model Aliases (recommended for -m flag)
| Alias | Resolves to | Use case |
|---|---|---|
auto |
gemini-3-pro-preview |
Default, auto-routing |
pro |
gemini-3-pro-preview |
Deep reasoning |
flash |
gemini-3-flash-preview |
Fast agentic coding |
flash-lite |
gemini-2.5-flash-lite |
Lowest latency/cost |
Full Model IDs
Gemini 3 (Preview):
gemini-3-pro-preview- Most powerful, deep reasoninggemini-3-flash-preview- Best for agentic coding (78% SWE-bench), 1/4 cost of Pro
Gemini 2.5 (GA):
gemini-2.5-pro- Stable, balanced performancegemini-2.5-flash- Stable, fastgemini-2.5-flash-lite- Lowest latency and cost
Headless Mode Tool Restrictions
In non-interactive mode (positional query or -p flag), Gemini restricts certain tools by default:
| Default | Excluded: shell, edit, write_file, web_fetch |
|---|---|
--approval-mode auto_edit |
Excluded: shell only |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 125 lines · 121 tokens per session scan A a754a2777554
gemini-cli is a skill published in the GitHub repository fprochazka/claude-code-plugins (11 stars, last pushed 4d ago), licensed MIT. It adds 121 tokens to every session and 1,137 once invoked, about $0.0006 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…