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 instructions/elyin/gemini-bridge/claude-mdgit clone --depth 1 https://github.com/eLyiN/gemini-bridgeWrote 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/instructions/elyin/gemini-bridge/claude-md)<a href="https://agentmods.dev/instructions/elyin/gemini-bridge/claude-md"><img src="https://agentmods.dev/badge/instructions/elyin/gemini-bridge/claude-md.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.02803 | $0.02803 |
| Opus 5 | $0.01401 | $0.01401 |
| Sonnet 5 | $0.00561 | $0.00561 |
| Haiku 4.5 | $0.00280 | $0.00280 |
Grade C, and why
gemini-bridge CLAUDE.md scanned grade C 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf dist/ build/ *.egg-info Copies of this mod
1 near-identical copy found in the catalogue:
- gemini-bridge CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Gemini Bridge is a lightweight MCP (Model Context Protocol) server that enables Claude Code to interact with Google's Gemini AI through the official CLI. The project follows extreme simplicity principles from Carmack and Torvalds - doing ONE thing well: bridging Claude to Gemini CLI.
Key Characteristics:
- Zero API costs (uses free Gemini CLI)
- Stateless architecture with no session management
- Direct subprocess integration for optimal performance
- Inline file guardrails with optional delegation to Gemini CLI's
@pathexpansion - Production-ready with professional CI/CD automation
Development Commands
Prerequisites
- Gemini CLI:
npm install -g @google/gemini-cli - Authentication:
gemini auth login - Verify:
gemini --version
Installation & Setup
Development Mode:
# Clone and install in development mode
git clone https://github.com/shelakh/gemini-bridge.git
cd gemini-bridge
pip install -e .
# Run directly from source
python -m src
Production Installation:
# Install from PyPI
pip install gemini-bridge
# Or use uvx (recommended)
uvx gemini-bridge
Claude Code Integration:
# Production installation (recommended)
claude mcp add gemini-bridge -s user -- uvx gemini-bridge
# Development mode (from local source)
claude mcp add gemini-bridge -s user -- python -m src
Testing & Verification
# Test CLI availability
gemini --version
# Test basic functionality
python -c "from src.mcp_server import execute_gemini_simple; print(execute_gemini_simple('Hello', '.'))"
# Test package installation
python -c "import src; print(f'Gemini Bridge v{src.__version__}')"
# Run automated tests
pytest
Build & Distribution
# Clean build
rm -rf dist/ build/ *.egg-info
# Build package
uvx --from build pyproject-build
# Verify build
pip install dist/*.whl
python -c "import src; print('Package works!')"
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.
- 5d ago First seen · 287 lines · 2,803 tokens per session scan C 6fbf9721a93c
gemini-bridge CLAUDE.md is an instructions file published in the GitHub repository eLyiN/gemini-bridge (94 stars, last pushed 2mo ago), licensed MIT. It adds 2,803 tokens to every session, about $0.0140 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).