Borrowing it
Nothing to install: this file belongs to VinnyVanGogh/gemini-code-assist-mcp. 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/VinnyVanGogh/gemini-code-assist-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/VinnyVanGogh/gemini-code-assist-mcpWrote 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/vinnyvangogh/gemini-code-assist-mcp/claude-md)<a href="https://agentmods.dev/instructions/vinnyvangogh/gemini-code-assist-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/vinnyvangogh/gemini-code-assist-mcp/claude-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.01761 | $0.01761 |
| Opus 5 | $0.00881 | $0.00881 |
| Sonnet 5 | $0.00352 | $0.00352 |
| Haiku 4.5 | $0.00176 | $0.00176 |
Grade A, and why
gemini-code-assist-mcp CLAUDE.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.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Core Principles
KISS (Keep It Simple, Stupid): Simplicity should be a key goal in design. Choose straightforward solutions over complex ones whenever possible. Simple solutions are easier to understand, maintain, and debug.
YAGNI (You Aren't Gonna Need It): Avoid building functionality on speculation. Implement features only when they are needed, not when you anticipate they might be useful in the future.
Dependency Inversion: High-level modules should not depend on low-level modules. Both should depend on abstractions. This principle enables flexibility and testability.
Open/Closed Principle: Software entities should be open for extension but closed for modification. Design your systems so that new functionality can be added with minimal changes to existing code.
🧱 Code Structure & Modularity
- Never create a file longer than 500 lines of code. If a file approaches this limit, refactor by splitting it into modules or helper files.
- Functions should be short and focused sub 50 lines of code and have a single responsibility.
- Classes should be short and focused sub 50 lines of code and have a single responsibility.
- Organize code into clearly separated modules, grouped by feature or responsibility.
Architecture
Strict vertical slice architecture with tests that live next to the code they test.
src/project/ init.py main.py tests/test_main.py conftest.py module_one/ (eg. database, core, auth) init.py module_one.py tests/ test_module_one.py module_two/ (eg. api, ui, cli) init.py module_two.py tests/ test_module_two.py
features/ (eg. business logic, tools, etc.)
feature_one/
__init__.py
feature.py
tests/
test_feature.py
Features can also be part of moduels if the module for example is a api integration or a cli tool.
eg src/project/ module_one/ (api integration with crm service) init.py module_one.py tests/ test_module_one.py features/ feature_one/ (CRM service integration slice) init.py feature.py tests/ test_feature.py
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 · 278 lines · 1,761 tokens per session scan A 1f7b531da44c
gemini-code-assist-mcp CLAUDE.md is an instructions file published in the GitHub repository VinnyVanGogh/gemini-code-assist-mcp (8 stars, last pushed 1y ago), licensed MIT. It adds 1,761 tokens to every session, about $0.0088 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.