Borrowing it
Nothing to install: this file belongs to Prof-Harita/terminaI. 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/Prof-Harita/terminaI/main/.gemini/commands/code-guide.tomlgit clone --depth 1 https://github.com/Prof-Harita/terminaIWrote 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/commands/prof-harita/terminai/code-guide)<a href="https://agentmods.dev/commands/prof-harita/terminai/code-guide"><img src="https://agentmods.dev/badge/commands/prof-harita/terminai/code-guide/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/commands/prof-harita/terminai/code-guide"><img src="https://agentmods.dev/badge/commands/prof-harita/terminai/code-guide.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.00000 | $0.00445 |
| Opus 5.5 | $0.00000 | $0.00178 |
| Sonnet 5.5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
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 1mo 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 code-guide — 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 — 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-startedfolder. -
Consult Documentation and Specific Folders: Before answering, you MUST first consult any relevant documentation within the
docsfolder. Base all your code-related answers exclusively on the contents of the following folders:integration-tests,packages, andscripts. -
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.
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.
- 1mo ago First seen · 40 lines · 0 tokens per session scan A d1b7eacb0d9f
code-guide is a command published in the GitHub repository Prof-Harita/terminaI (425 stars, last pushed yesterday), 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. It is 100% identical to code-guide, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
client-education
Produce patient education handouts on specific dietary topics, conditions, or lifestyle modifications.
patient-education
Generate patient education materials including post-procedure instructions, oral hygiene education, and condition-specific handouts.
job-hazard-analysis
Break a task into steps, surface the hazard at each step, and propose controls ordered by the hierarchy of controls rather than defaulting to PPE.
toolbox-talk
Build a five-minute toolbox talk from a topic, a season, or a recent incident — written in plain language for the crew who has to act on it.
onboarding-doc
Create onboarding materials tailored to specific roles.
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.