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/biggora/claude-plugins-registry/gemini-clinpx skills add biggora/claude-plugins-registry --skill gemini-cligit clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote 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/biggora/claude-plugins-registry/gemini-cli)<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/gemini-cli"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/gemini-cli.svg" alt="Measured on agentmods" 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 | $0.00176 | $0.02730 |
| Opus 5 | $0.00088 | $0.01365 |
| Sonnet 5 | $0.00035 | $0.00546 |
| Haiku 4.5 | $0.00018 | $0.00273 |
Grade B, and why
gemini-cli scanned grade B 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Location: `~/.gemini/settings.json` (global) or `<project>/.gemini/settings.json` How it starts
The opening of the file, as written. The whole thing — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemini CLI Skill
Gemini CLI is an open-source AI agent that brings Gemini models directly into the terminal. It supports interactive REPL sessions, headless/non-interactive scripting, MCP servers, custom slash commands, and extension-based workflows.
Reference files (read when needed):
references/commands.md— slash commands, built-in commands referencereferences/configuration.md— settings.json, GEMINI.md, environment variablesreferences/mcp-and-extensions.md— MCP server setup, extensions authoringreferences/headless-and-scripting.md— non-interactive mode, automation, CI/CD patterns
Installation
# Instant use, no install
npx @google/gemini-cli
# Global install (recommended)
npm install -g @google/gemini-cli
# macOS/Linux via Homebrew
brew install gemini-cli
# Specific channels
npm install -g @google/gemini-cli@latest # stable (weekly Tuesdays)
npm install -g @google/gemini-cli@preview # preview (weekly, less vetted)
npm install -g @google/gemini-cli@nightly # nightly (daily builds)
Authentication
Choose one method:
Option 1: Google OAuth (recommended for individuals)
gemini # → choose "Login with Google" → browser flow
- Free: 60 req/min, 1,000 req/day
- No API key needed
Option 2: Gemini API Key
export GEMINI_API_KEY="your_key_here"
# Get key: https://aistudio.google.com/apikey
gemini
- Free: 1,000 req/day (Gemini Flash/Pro mix)
- Can also store in
~/.gemini/.envor./.gemini/.env
Option 3: Application Default Credentials (ADC)
gcloud auth application-default login
gemini
- Uses Google Cloud ADC — no API key needed
- Best for developers already using Google Cloud
Option 4: Vertex AI (enterprise)
export GOOGLE_GENAI_USE_VERTEXAI=true
export GOOGLE_CLOUD_PROJECT="your-project-id"
gcloud auth application-default login
gemini
Basic Usage
# Start interactive session in current directory
gemini
# Include extra directories as context
gemini --include-directories ../lib,../docs
# Use a specific model
gemini -m gemini-2.5-flash
gemini -m gemini-2.5-pro
# Non-interactive: single prompt, then exit
gemini -p "Explain the architecture of this codebase"
# Reference files in prompt with @ syntax
gemini -p "Review @./src/auth.py for security issues"
# Pipe stdin
cat error.log | gemini -p "What went wrong here?"
git diff --cached | gemini -p "Write a concise commit message"
What ships with it
4 files 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.
- 3d ago First seen · 384 lines · 176 tokens per session scan B a4f54de10ff5
gemini-cli is a skill published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 5d ago), licensed MIT. It adds 176 tokens to every session and 2,730 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…