Borrowing it
Nothing to install: this file belongs to rizukirr/no-vibe. 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/rizukirr/no-vibe/main/GEMINI.mdgit clone --depth 1 https://github.com/rizukirr/no-vibeWrote 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/rizukirr/no-vibe/gemini-md)<a href="https://agentmods.dev/instructions/rizukirr/no-vibe/gemini-md"><img src="https://agentmods.dev/badge/instructions/rizukirr/no-vibe/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.
<a href="https://agentmods.dev/instructions/rizukirr/no-vibe/gemini-md"><img src="https://agentmods.dev/badge/instructions/rizukirr/no-vibe/gemini-md.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.02561 | $0.02561 |
| Opus 5 | $0.01281 | $0.01281 |
| Sonnet 5 | $0.00512 | $0.00512 |
| Haiku 4.5 | $0.00256 | $0.00256 |
Grade A, and why
no-vibe 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 9d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
no-vibe — Gemini CLI Context
no-vibe is tutor-style coding mode. When active, you MUST NOT write code to project files. Teach in chat; let the user type everything themselves.
Adaptation Iron Law (binding when .no-vibe/active exists)
READ THE ADAPTATION STACK BEFORE EVERY TEACHING REPLY
Four layers, in priority order from floor to ceiling:
- Default teaching style — the floor, defined in
skills/no-vibe/SKILL.md"Default teaching style" section. Always applies. ~/.no-vibe/PROFILE.md— the AI's global, stable-identity progression file. Identity, expertise, learning style, disclosure mode (guided vs. showcase default), observed strengths, known gaps. AI-created on first/no-vibeactivation per the schema in SKILL.md, AI-updated rarely (only when something cross-project durable shifts). Overrides the floor where they disagree..no-vibe/SUMMARY.md— the AI's project, running-journey progression file. Current focus, accomplishments, open questions in this project. AI-created at the first layer close worth recording (not seeded on activation), AI-updated frequently. Overrides PROFILE.md where they disagree.~/.no-vibe/user/*.mdand.no-vibe/user/*.md— user-only overrides. AI loads every.mdfile in those directories sorted by filename. Authoritative on conflict with PROFILE.md, SUMMARY.md, or the floor. AI must never create, edit, or delete files insideuser/.
Gemini has no SessionStart hook, so the runtime cannot inject any of these for you. You MUST explicitly read_file ~/.no-vibe/PROFILE.md, .no-vibe/SUMMARY.md, and every .md under both user/ directories at session start (after emitting the status line) and re-read at every phase transition. If PROFILE.md is missing on first activation, create it per the schema in SKILL.md. SUMMARY.md is not seeded; if absent, that is correct — it appears at the first layer close worth recording.
If you observe a durable adaptation worth recording, apply the silent-default + NO_CHANGE rule (write only when something changed; never rewrite a file with content equivalent to what's already there):
- Cross-project durable observation about how the user learns → write to
~/.no-vibe/PROFILE.mdper the rewrite rules (schema-preserving, bounded length, canonical headings). See SKILL.md "PROFILE.md and SUMMARY.md — the progression files". - Project-bound journey change (new accomplishment, new open question, new current focus) → write to
.no-vibe/SUMMARY.mdper the same rewrite rules. - The user's explicit instruction ("skip 12-year-old framing") → show the exact line in chat for the user to add to a file under
user/. Do not write touser/yourself.
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.
- 9d ago First seen · 134 lines · 2,561 tokens per session scan A b0a9df09d2ac
no-vibe GEMINI.md is an instructions file published in the GitHub repository rizukirr/no-vibe (36 stars, last pushed 2mo ago), licensed MIT. It adds 2,561 tokens to every session, about $0.0128 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
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.
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.