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/gemini-cli-extensions/code-review/gemini-mdgit clone --depth 1 https://github.com/gemini-cli-extensions/code-reviewWhat 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.00095 | $0.00095 |
| Opus 5 | $0.00048 | $0.00048 |
| Sonnet 5 | $0.00019 | $0.00019 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
code-review 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 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.
What it actually says
The code-review extension introduces the following commands:
/code-review
When a user requests that code changes be reviewed, this command should be the preferred way to do so.
/pr-review
When a user requests that pr to be reviewed, look at user provided input "{{args}}" and environment variables to see if $REPOSITORY, $PULL_REQUEST_NUMBER, and $ADDITIONAL_CONTEXT are set. If any variables are missing or have ambiguity, ask user for clarification.
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 · 10 lines · 95 tokens per session scan A 60c0c575bd5f
code-review GEMINI.md is an instructions file published in the GitHub repository gemini-cli-extensions/code-review (532 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 95 tokens to every session, about $0.0005 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
security GEMINI.md
Instructions for gemini-cli-extensions/security, covering standard operating procedures: security analysis guidelines, persona and guiding principles, skillset: permitted tools & investigation, skillset: sast vulnerability analysis and 1.1. hardcoded secrets.
jules GEMINI.md
Instructions for gemini-cli-extensions/jules, covering jules extension, command: /jules, activation and response, starting a jules task and jules-related queries.
pickle-rick-extension GEMINI.md
Instructions for galdawave/pickle-rick-extension, covering pickle rick extension, project overview, key components, 1. configuration and 2. persona definition.
odin-gemini-cli-extension AGENTS.md
Instructions for OutlineDriven/odin-gemini-cli-extension, covering gemini code agent manual, token-efficient cli output, core system & file ops, search & discovery and code manipulation.
self-command GEMINI.md
Instructions for stevenAthompson/self-command, covering self command extension, tools, 1. selfcommand, 2. geminisleep and 3. watchlog.
run-long-command GEMINI.md
Instructions for stevenAthompson/run-long-command, covering run long command extension, usage, tool signature, example and how it works.