Borrowing it
Nothing to install: this file belongs to yideng-xl/gemini-cli-hud. 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/yideng-xl/gemini-cli-hud/main/GEMINI.mdgit clone --depth 1 https://github.com/yideng-xl/gemini-cli-hudWrote 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/yideng-xl/gemini-cli-hud/gemini-md)<a href="https://agentmods.dev/instructions/yideng-xl/gemini-cli-hud/gemini-md"><img src="https://agentmods.dev/badge/instructions/yideng-xl/gemini-cli-hud/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.1 | $0.00342 | $0.00342 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
gemini-cli-hud 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 8d 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
Gemini CLI HUD
This extension provides a real-time, bottom-sticky heads-up display (HUD) at the bottom of your terminal during Gemini CLI sessions.
What It Shows
- Active Model: Current model name (e.g.,
gemini-3-flash) - Context Usage: Progress bar with percentage and token counts (e.g.,
Ctx: ████░░ 42% (420K/1.0M)) - Tool Calls: Claude-HUD style tool tracking (e.g.,
✓ run_shell_command ×17 | ✓ replace ×1) - GEMINI.md Count: Number of loaded GEMINI.md files (project + global + extensions)
- Extensions Count: Number of installed Gemini CLI extensions
- Active Skill: Currently activated skill/extension
- Session Timer: Elapsed time since session start
How It Works
The HUD uses DECSTBM (Set Top and Bottom Margins) to reserve the bottom rows of your terminal. Gemini CLI's content scrolls in the region above, while the HUD stays fixed at the bottom.
- Hook (
hook.js): Invoked synchronously by Gemini CLI on each event. Renders HUD to/dev/tty. - Daemon (
daemon.js): Background process that maintains HUD state. Communicates with hook via Unix socket.
Notes
- The HUD updates on each Gemini CLI event (SessionStart, AfterModel, AfterTool) — no background polling.
- If the terminal is resized, the HUD adjusts on the next event.
- Run
resetafter exiting Gemini CLI to clear the DECSTBM scroll region if needed.
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.
- 8d ago First seen · 27 lines · 342 tokens per session scan A 207ef25fd0a5
gemini-cli-hud GEMINI.md is an instructions file published in the GitHub repository yideng-xl/gemini-cli-hud (8 stars, last pushed 3mo ago), licensed MIT. It adds 342 tokens to every session, about $0.0017 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-31.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.