Borrowing it
Nothing to install: this file belongs to FojleRabbiRabib/gemini-bridge. 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/FojleRabbiRabib/gemini-bridge/master/AGENTS.mdgit clone --depth 1 https://github.com/FojleRabbiRabib/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/fojlerabbirabib/gemini-bridge/agents-md)<a href="https://agentmods.dev/instructions/fojlerabbirabib/gemini-bridge/agents-md"><img src="https://agentmods.dev/badge/instructions/fojlerabbirabib/gemini-bridge/agents-md/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/instructions/fojlerabbirabib/gemini-bridge/agents-md"><img src="https://agentmods.dev/badge/instructions/fojlerabbirabib/gemini-bridge/agents-md.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.00799 | $0.00799 |
| Opus 5 | $0.00400 | $0.00400 |
| Sonnet 5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
gemini-bridge AGENTS.md 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 8d 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.
This is a copy
100% identical to gemini-bridge AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
The package lives under src/, with mcp_server.py defining the FastMCP tools and __main__.py exposing the module entry point. Project metadata, dependency pins, and the gemini-bridge console script are declared in pyproject.toml. Reference docs and policies (README.md, CONTRIBUTING.md, SECURITY.md) sit in the repository root. Create new modules inside src/ and keep supporting assets (sample configs, text fixtures) alongside their consumers.
Build, Test, and Development Commands
pip install -e .— install in editable mode for local development.python -m src— launch the MCP server directly; useCTRL+Cto exit.uvx gemini-bridge— run the packaged CLI exactly as downstream clients will.uvx --from build pyproject-build— build distribution artifacts before publishing or testing installation. Run commands from the project root to ensure relative paths resolve correctly.
Coding Style & Naming Conventions
Follow PEP 8 with 4-space indentation and an 88-character target line length. Use descriptive, lowercase snake_case for functions and variables, UPPER_SNAKE_CASE for constants, and reserve CamelCase for classes. Keep functions small, add docstrings describing intent, and include type hints on public interfaces. Prefer expressive log messages over inline comments; only annotate logic that is non-obvious.
Testing Guidelines
Validate changes by exercising all three MCP tools: consult_gemini, consult_gemini_with_files, and web_search. Run python -m src for the stdio server and uvx gemini-bridge -- --help or a sample prompt to confirm CLI wiring. Automated tests are located under tests/, targeting pytest, and mirror module names (e.g., tests/test_mcp_server.py). Cover environment-sensitive paths such as _normalize_model_name, _get_timeout, and the new web_search function. Document manual test steps in your PR.
Commit & Pull Request Guidelines
Commit messages follow Conventional Commit prefixes (feat:, fix:, chore:, docs:) and should explain the motivation. Keep commits atomic and focused on one concern. Pull requests must include a concise summary, linked issues, and a brief testing log (commands run, expected vs. actual behavior). Request a review once CI (when available) passes and respond to feedback with follow-up commits rather than force-pushes.
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.
- 8d ago First seen · 37 lines · 799 tokens per session scan A 49ce4542a25d
gemini-bridge AGENTS.md is an instructions file published in the GitHub repository FojleRabbiRabib/gemini-bridge (0 stars, last pushed 4mo ago), licensed MIT. It adds 799 tokens to every session, about $0.0040 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gemini-bridge AGENTS.md, differing in 0 lines, and is treated as a copy.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.