Borrowing it
Nothing to install: this file belongs to xenitV1/Antigravity-Workflows. 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/xenitV1/Antigravity-Workflows/main/GEMINI.mdgit clone --depth 1 https://github.com/xenitV1/Antigravity-WorkflowsWrote 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/xenitv1/antigravity-workflows/gemini-md)<a href="https://agentmods.dev/instructions/xenitv1/antigravity-workflows/gemini-md"><img src="https://agentmods.dev/badge/instructions/xenitv1/antigravity-workflows/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/xenitv1/antigravity-workflows/gemini-md"><img src="https://agentmods.dev/badge/instructions/xenitv1/antigravity-workflows/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.02676 | $0.02676 |
| Opus 5.5 | $0.01070 | $0.01070 |
| Sonnet 5.5 | $0.00535 | $0.00535 |
| Haiku 4.5 | $0.00268 | $0.00268 |
Grade A, and why
Antigravity-Workflows 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 1mo 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEMINI.md - Maestro Configuration
Version 4.0 - Maestro AI Development Orchestrator This file defines how the AI behaves in this workspace.
� CRITICAL: AGENT & SKILL PROTOCOL (START HERE)
MANDATORY: You MUST read the appropriate agent file and its skills BEFORE performing any implementation. This is the highest priority rule.
1. Modular Skill Loading Protocol
Agent activated → Check frontmatter "skills:" field
│
└── For EACH skill:
├── Read SKILL.md (INDEX only)
├── Find relevant sections from content map
└── Read ONLY those section files
- Selective Reading: DO NOT read ALL files in a skill folder. Read
SKILL.mdfirst, then only read sections matching the user's request. - Rule Priority: P0 (GEMINI.md) > P1 (Agent .md) > P2 (SKILL.md). All rules are binding.
2. Enforcement Protocol
- When agent is activated:
- ✅ READ all rules inside the agent file.
- ✅ CHECK frontmatter
skills:list. - ✅ LOAD each skill's
SKILL.md. - ✅ APPLY all rules from agent AND skills.
- Forbidden: Never skip reading agent rules or skill instructions. "Read → Understand → Apply" is mandatory.
�📥 REQUEST CLASSIFIER (STEP 2)
Before ANY action, classify the request:
| Request Type | Trigger Keywords | Active Tiers | Result |
|---|---|---|---|
| QUESTION | "what is", "how does", "explain" | TIER 0 only | Text Response |
| SURVEY/INTEL | "analyze", "list files", "overview" | TIER 0 + Explorer | Session Intel (No File) |
| SIMPLE CODE | "fix", "add", "change" (single file) | TIER 0 + TIER 1 (lite) | Inline Edit |
| COMPLEX CODE | "build", "create", "implement", "refactor" | TIER 0 + TIER 1 (full) + Agent | {task-slug}.md Required |
| DESIGN/UI | "design", "UI", "page", "dashboard" | TIER 0 + TIER 1 + Agent | {task-slug}.md Required |
| SLASH CMD | /create, /orchestrate, /debug | Command-specific flow | Variable |
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.
- 1mo ago First seen · 248 lines · 2,676 tokens per session scan A cb19ac0fd9d4
Antigravity-Workflows GEMINI.md is an instructions file published in the GitHub repository xenitV1/Antigravity-Workflows (127 stars, last pushed 9mo ago), licensed MIT. It adds 2,676 tokens to every session, about $0.0107 per session on Opus 5.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
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).
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.
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).
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.