geminiignore-finops
Optimizes the agent's token usage to reduce costs. Helps control what the agent considers to be more efficient.
What it does
This assistant creates and improves a special file called `.geminiignore`. It helps the AI focus on what's important by ignoring unnecessary files like machine code, logs, and packages, to save time and money.
When to use it
- ✓When starting a new project with AI.
- ✓When the AI is taking too long or costing too much.
- ✓When the AI is reading things it shouldn't, like configuration or system files.
Example of what to ask your AI
“Create a `.geminiignore` file for my Node.js project that ignores dependencies and build files.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
It first understands which languages your project uses. Then, it adds rules to a `.geminiignore` file to ignore files the AI doesn't need to see, like automatically generated code or log files.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill geminiignore-finopsOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/geminiignore-finops/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
GeminiIgnore FinOps Setup & Optimization
Overview
A skill to construct, refine, and maintain high-performance .geminiignore files across diverse tech stacks. By filtering out machine-generated code, heavy logs, package locks, and binary assets, this skill optimizes the AI agent's context window, accelerates processing speed, and reduces token consumption costs (FinOps).
When to Use This Skill
- Use when initializing a new repository or workspace for pair-programming with AI agents.
- Use when the AI context window is reaching its limits or when billing optimization (FinOps) is a priority.
- Use when the AI agent is accidentally reading build outputs, lock files, databases, or binary media.
How It Works
Step 1: Analyze the Workspace Tech Stack
Detect the languages, frameworks, and dependency managers present in the project (e.g., Node.js, Python, PHP, Dart/Flutter, Rust).
Step 2: Initialize or Update the .geminiignore File
Create a .geminiignore file at the root of the active workspace. If one already exists, review it to add missing categories.
Step 3: Implement the 7 Core Rules
Add rules divided into the following categories to filter out unnecessary machine noise while keeping human-written code visible:
- System & Editor Noise: Block OS temp files (
.DS_Store,Thumbs.db) and user-specific IDE caches (.idea/,.vscode/*, Xcode user data). - Dependency Folders & Lock Files: Ignore third-party package directories (
node_modules/,vendor/) and giant machine-generated lock files (package-lock.json,yarn.lock,Cargo.lock,composer.lock). - Build & Target Output: Block compiled folders (
dist/,build/,.next/,.nuxt/). - Caches & Tool Metadata: Block compiler caches (
.tsbuildinfo,.vite/,.pytest_cache/,.eslintcache). - Binary & Rich Assets: Block media types (
*.png,*.pdf,*.mp4,*.woff2) to prevent triggering expensive vision/multimodal tokens. - Local Databases & Logs: Block log files (
*.log) and SQL dumps or local SQLite DBs (*.sqlite,*.db). - Compiled Binaries & Mobile Builds: Block mobile package files (
*.apk,*.ipa) and compiled binaries (*.class,*.pyc,*.dll).
Step 4: Validate Exclusions
Verify that the AI can still see critical configuration blueprints (like .env.example, package.json, composer.json, pyproject.toml) but ignores the actual .env files and compilation artifacts.
Examples
Example 1: Standard Universal .geminiignore Template
Here is a recommended baseline configuration for a multi-language project:
# ==============================================================================
# .geminiignore - BASELINE DE FINOPS E ARQUITETURA
# ==============================================================================
# 1. SISTEMA OPERACIONAL E IDEs
.DS_Store
Thumbs.db
Desktop.ini
$RECYCLE.BIN/
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
.idea/
*.iml
.gradle/
local.properties
.history/
# 2. DEPENDÊNCIAS (ECONOMIA DE TOKENS EM LOCK FILES)
node_modules/
package-lock.json
yarn.lock
pnpm-lock.yaml
vendor/
composer.lock
venv/
.venv/
env/
.env
.env.*
!.env.example
poetry.lock
Cargo.lock
pubspec.lock
# 3. BUILDS E EXPORTAÇÕES
dist/
build/
out/
target/
.next/
.nuxt/
.output/
bin/
obj/
# 4. CACHES DE FRAMEWORKS
.vite/
.parcel-cache/
.eslintcache
.babel-cache/
.tsbuildinfo
.turbo/
.pytest_cache/
.ruff_cache/
storage/framework/
storage/logs/
# 5. ASSETS BINÁRIOS E MULTIMÍDIA EXTREMOS
*.png
*.jpg
*.jpeg
*.gif
*.webp
*.svg
*.ico
*.psd
*.fig
*.pdf
*.zip
*.tar.gz
*.woff
*.woff2
*.ttf
# 6. BANCOS DE DADOS E LOGS
*.log
*.db
*.sqlite
*.sqlite3
*.sql
*.sql.gz
# 7. ARQUIVOS COMPILADOS
*.apk
*.aab
*.ipa
*.jar
*.class
*.pyc
__pycache__/
*.so
*.dylib
*.dll
*.exe
*.js.map
*.css.map
Best Practices
- ✅ Ignore dependency lock files: Standard lock files (e.g.,
package-lock.json,yarn.lock) contain thousands of lines of redundant package resolution trees. Ignoring them is the single largest FinOps win. - ✅ Keep configurations visible: Ensure manifests like
package.json,composer.json,Cargo.toml, andpyproject.tomlare NEVER ignored, as the AI needs them to understand dependencies. - ✅ Whitelist config examples: Use rules like
!.env.examplealongside.envignores so the AI understands configuration structure without exposing credentials.
…
FAQ
What is a `.geminiignore` file?
It's a configuration file that tells the AI which files and folders to ignore in a project, so it can focus on the important code.
Why does this save money?
The AI uses 'tokens' to process information. Ignoring large, unnecessary files reduces the number of tokens used, lowering the cost.
Is this the same as `.gitignore`?
No. `.gitignore` is for Git (version control) to not track files. `.geminiignore` is for the AI to ignore files when analyzing your code.
Details
Original description by the author
Configure and optimize .geminiignore files for AI context window efficiency and token cost reduction (FinOps).
Popularity
- GitHub stars
- 48k
- Ranking position
- #3097
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
agent-architecture-audit
Makes your agent check if everything is working correctly. It finds and fixes problems in AI systems, ensuring they perform as expected.
affaan-m/ECC
agent-eval
Helps your agent compare different AI coding tools. It measures which one is faster, cheaper, and more reliable for specific tasks.
affaan-m/ECC
agent-harness-construction
Makes your agent better understand how to perform tasks. It optimizes the tools and instructions the agent uses to increase its chances of success.
affaan-m/ECC