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/ksprashu/gemini-cli-config/gemini-mdgit clone --depth 1 https://github.com/ksprashu/gemini-cli-configWrote 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/ksprashu/gemini-cli-config/gemini-md)<a href="https://agentmods.dev/instructions/ksprashu/gemini-cli-config/gemini-md"><img src="https://agentmods.dev/badge/instructions/ksprashu/gemini-cli-config/gemini-md.svg" alt="Measured on agentmods" 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 | $0.00618 | $0.00618 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
gemini-cli-config 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical preferences when building out applications
Preferred Gemini models and order of priority
Use the following Gemini models as per the defined priority whenever you have to work on the kind of tasks below, unless specifically instructed otherwise.
-
Image Generation
- gemini-3-pro-image-preview (Nano Banana Pro) [API: generate_content]
- gemini-2.5-flash-image (Nano Banana) [API: generate_content]
- imagen-4.0-ultra-generate-001 [API: generate_images]
- imagen-4.0-generate-001 [API: generate_images]
-
General Purpose/Verification/Multi-model input and analysis
- gemini-3-pro-preview [API: generate_content]
- gemini-3-flash-preview [API: generate_content]
- gemini-2.5-pro [API: generate_content]
- gemini-2.5-flash [API: generate_content]
Preferred package managers and stacks
Use the following package manages and stacks when working on the following programming languages unless otherwise instructed
- Python
- FastAPI for any backend work exposing services / APIs
- Use 'uv' for managing dependencies and adding / removing packages, and managing the virtual environment
- Use Gradio for building any sample UI apps and prototyping frontends for AI apps
- Javascript / Typescript / Nodejs
- Use 'pnpm' for managing packages and dependencies
- Gemini SDK / API
- When using Gemini use the Google Gen AI SDK - '@google/genai' for javascript / typscript, 'google-genai' for python, etc. This is non negotiable for AI apps on Gemini models.
- Refer to https://ai.google.dev/gemini-api/docs/quickstart for the docs on Google Gen AI SDK.
- Use Google ADK - 'google-adk' in python, '@google/adk' for typescript / javascript etc. Refer to https://google.github.io/adk-docs/get-started/ for docs.
General programming guidelines
- Always document functions with docstrings, including desription, what it does and import / return params
- Always use compile-time type-safety in any language that supports it, including Python and Javascript.
- Use linters, prettifiers, and static code checks at all times and set it up in the build rules of the language project we are working on, if not already present.
- Prefer Google Style guides for Javascript, Typescript, Python, Go etc. at all times and if unspecified, unless the project uses a different style either inferred or documented.
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.
- 4d ago First seen · 39 lines · 618 tokens per session scan A 903b6877af0d
gemini-cli-config GEMINI.md is an instructions file published in the GitHub repository ksprashu/gemini-cli-config (22 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 618 tokens to every session, about $0.0031 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.