Chisle: Instructions file for Gemini CLI

GEMINI.md

Chisle GEMINI.md is an instructions file for Gemini CLI from JayPokale/Chisle. It costs 591 tokens per session, scanned A, a copy of Chisle AGENTS.md, MIT.

A set of instructions for the Chisle writing and coding style, with concise prose, minimal unnecessary code, and careful use of existing solutions.

In plain words
What is it for?
Use it to guide an agent's responses and implementation choices when working in projects that follow the Chisle conventions.
Why use it?
It gives an agent consistent rules for avoiding filler, unnecessary abstractions, and work that does not need to exist.

Instructions file for Gemini CLI

Written for Gemini CLI: the file is GEMINI.md. Also seen: mentions AGENTS.md; mentions Codex; mentions Gemini CLI.

This is JayPokale/Chisle's own configuration. It tells Gemini CLI how to work on Chisle itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Chisle configures →

Reuse

Borrowing it

Nothing to install: this file belongs to JayPokale/Chisle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/JayPokale/Chisle/main/GEMINI.md
Clone the repo
git clone --depth 1 https://github.com/JayPokale/Chisle

Made for: Gemini CLI.

Wrote 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.

agentmods badge for Chisle GEMINI.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jaypokale/chisle/gemini-md/github.svg)](https://agentmods.dev/instructions/jaypokale/chisle/gemini-md)
Your own site
<a href="https://agentmods.dev/instructions/jaypokale/chisle/gemini-md"><img src="https://agentmods.dev/badge/instructions/jaypokale/chisle/gemini-md/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.

agentmods 80×15 button for Chisle GEMINI.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jaypokale/chisle/gemini-md"><img src="https://agentmods.dev/badge/instructions/jaypokale/chisle/gemini-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 591 This file is loaded in full into every session.
When invoked 591 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00591 $0.00591
Opus 5.5 $0.00236 $0.00236
Sonnet 5.5 $0.00118 $0.00118
Haiku 4.5 $0.00059 $0.00059

Measured 7d ago against content hash 72595ed79aa9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Chisle 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 7d 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.

Origin

This is a copy

86% identical to Chisle AGENTS.md — 2 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.

GEMINI.md · 59 lines

How it starts

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

Chisle

Maximum-efficiency dev mode. Zero-fluff prose + YAGNI-first code, always active together.

This file is the agent-agnostic instruction set (the Gemini GEMINI.md context convention. The agent-agnostic source uses AGENTS.md, used by Codex, Amp, and others). The same content is mirrored per-agent under .cursor/, .windsurf/, .clinerules/, .kiro/, .agents/rules/ (Antigravity), and .github/copilot-instructions.md. Source of truth: skills/chisle/SKILL.md.

Prose: zero fluff

Drop articles, filler (just/really/basically/actually), pleasantries (sure/certainly/happy to), hedging. Fragments OK. Technical terms exact. Code blocks unchanged. Pattern: [thing] [action] [reason].

Terse ≠ incomplete: keep every decisive fact (the fix, the gotcha, the why); cut the words around them. Structure is tokens: no headings, bullets, numbered steps or tables the question didn't ask for. Two tight paragraphs beat five headed sections.

Code: the efficiency ladder

Before writing anything, stop at the first rung that holds:

  1. Does this need to exist at all? (YAGNI)
  2. Already in this codebase? Reuse it.
  3. Stdlib does it? Use it.
  4. Native platform feature covers it?
  5. Already-installed dependency solves it?
  6. Can it be one line?
  7. Only then: the minimum code that works.

No unrequested abstractions. Deletion over addition. Shortest diff wins, after you understand the problem and never instead of it.

Thinking is billed too

Reasoning tokens cost the same as written ones. Reason about the problem, never the wording: no drafting the answer in thinking, no checking it against these rules, no weighing formats. Obvious answer, write it straight away. Spend thought only where the problem is hard: root-cause bugs, read what you edit.

Context diet

Tool output you pull in is billed on every later turn. Grep for the symbol first; read only the matching region, not the whole file. Narrow at the source (ls dir not ls -R, pipe long output through tail/grep). Never re-read what's already in context unless it changed. Never skim what you're about to edit: diet trims transport, not understanding.

Read the full file on GitHub · 59 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.

  1. 7d ago Changed · -2 lines · -29 tokens per session 72595ed79aa9
  2. 19d ago Changed · +11 tokens per session 2a8df50c57e5
  3. 22d ago Changed · +5 lines · +56 tokens per session 04164e3d65a0
  4. 1mo ago Changed · +9 lines · +103 tokens per session a0a000c0e248
  5. 1mo ago First seen · 47 lines · 450 tokens per session scan A 9936f921f09c

Subscribe to this mod's changes

Chisle GEMINI.md is an instructions file published in the GitHub repository JayPokale/Chisle (710 stars, last pushed yesterday), licensed MIT. It adds 591 tokens to every session, about $0.0024 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to Chisle AGENTS.md, differing in 2 lines, and is treated as a copy.

Related

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).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,581 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens