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/diegosouzapw/omniroute/gemini-mdgit clone --depth 1 https://github.com/diegosouzapw/OmniRouteWhat 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.00151 | $0.00151 |
| Opus 5 | $0.00076 | $0.00076 |
| Sonnet 5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
OmniRoute GEMINI.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 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.
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.
What it actually says
GEMINI.md
Single source of truth: all project rules for AI assistants live in
AGENTS.md. Read it in full before any change — it contains the 23 Hard Rules, quality gates, code conventions, file-placement / repo-root hygiene rules, the repository map and the local development access notes that used to live in this file.
Gemini-specific notes:
- Skills activate via the
activate_skilltool (skill metadata is loaded at session start and the full content is activated on demand). - There are no other Gemini-only rules today. Do not re-add project rules here — edit
AGENTS.mdinstead, so every assistant sees the same instructions.
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 · 14 lines · 151 tokens per session scan A 8ce18538a6fa
OmniRoute GEMINI.md is an instructions file published in the GitHub repository diegosouzapw/OmniRoute (59,841 stars, last pushed today), licensed MIT. It adds 151 tokens to every session, about $0.0008 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 instructions, from other repositories
EnterpriseAgentFramework AGENTS.md
Instructions for w8123/EnterpriseAgentFramework, covering reachai agent rules, 工作原则, windows powershell 与原生程序 utf-8 硬约束, 项目定位 and 关键目录.
trpc-agent-go AGENTS.md
AGENTS.md instructions for trpc-group/trpc-agent-go, covering agents.md, project overview, engineering principles, go design conventions and implementation workflow.
agentgateway copilot-instructions.md
Copilot instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.
nuwax AGENTS.md
Instructions for nuwax-ai/nuwax, covering ai agent system documentation, 系统概述, ai agent 架构, 核心组件 and ai 功能特性.
orbit CLAUDE.md
Instructions for schmitech/orbit, covering claude.md, project overview, commands, setup and running the server.
Cotal AGENTS.md
Instructions for Cotal-AI/Cotal, covering agents.md, what this is, read these first, commands and repository map.