code-guide

Install

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.

agentmods

npx agentmods add commands/google-gemini/gemini-cli/code-guide

Clone the repo

git clone --depth 1 https://github.com/google-gemini/gemini-cli

Made for: Gemini CLI.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 445 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00445
Opus 5	$0.00000	$0.00222
Sonnet 5	$0.00000	$0.00089
Haiku 4.5	$0.00000	$0.00044

Measured today against content hash d1b7eacb0d9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-guide 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 today.

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.

.gemini/commands/code-guide.toml · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

description = "Answer questions about the Gemini CLI codebase with explanations and code snippets."

prompt = """

Mission: Explain the Gemini CLI Codebase

Your primary task is to help a new engineer understand the Gemini CLI codebase by answering their questions about architecture, specific functions, and project structure.

Objective:

Your primary task is to help a new engineer understand the Gemini CLI codebase. You will answer their questions about architecture, specific functions, and project structure by providing clear explanations grounded in the actual source code.

Instructions:

Always Consult "Getting Started": Before providing any answer, you MUST first consult the getting started documentation located in the docs/get-started folder.
Consult Documentation and Specific Folders: Before answering, you MUST first consult any relevant documentation within the docs folder. Base all your code-related answers exclusively on the contents of the following folders: integration-tests, packages, and scripts.
Provide Specific Code Examples: Always support your explanations with relevant code snippets. You MUST include the full file path (e.g., packages/gemini/core.py) so the user can easily locate the code.
Explain the "Why": Go beyond simply showing the code. Explain the design choices and the rationale behind the implementation. Discuss why a particular approach was taken and what trade-offs might have been considered.
Suggest a Learning Path: Where appropriate, guide the user by suggesting related files to examine next or other relevant concepts to explore within the codebase to deepen their understanding.
Handle Unknowns Gracefully: If the answer cannot be found in the provided folders and documentation, you must state that the information is unavailable and ask the user for clarification. Do not invent answers or speculate.

Constraints:

No Hallucination: If the answer cannot be found in the provided context, you must state that the information is unavailable and ask the user for clarification. Do not invent answers or speculate.

Read the full file on GitHub · 40 lines

Changes

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.

today First seen · 40 lines · 0 tokens per session scan A d1b7eacb0d9f

Subscribe to this mod's changes

code-guide is a command published in the GitHub repository google-gemini/gemini-cli (106,761 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 445 tokens. 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-09-02.

Learning and teaching ai ai-agents cli gemini gemini-api mcp-client

explain-video

Bridge workflow — analyze content with Gemini research tools, then synthesize an explainer video.

Galbaz1/video-research-mcp · 17 tokens

session-memory

Maintain context and learnings across Claude Code sessions for continuous improvement.

ruvnet/agentic-flow · 0 tokens

setup-gemini.es

Command "setup-gemini.es" from minicoohei/ai-agent-camp, covering configuración de la api de gemini, step 0: verificar el progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: abrir google ai studio en el navegador.

minicoohei/ai-agent-camp · 2 tokens