Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/secondlifes/code-intel/gemini-mdgit clone --depth 1 https://github.com/SecondLifes/code-intelWhat 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 | $0.00362 | $0.00362 |
| Opus 5 | $0.00181 | $0.00181 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
code-intel 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 yesterday.
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
CodeIntel AI Spec-Kit — Gemini CLI / Antigravity Context
Gemini CLI builds its context from a hierarchy of GEMINI.md files — the
global ~/.gemini/GEMINI.md, then every GEMINI.md from the working
directory up to the project root. It does not read
.gemini/rules/project-rules.md on its own; that file is this kit's
hand-authored Gemini summary, and this file is what actually puts it in
front of the model.
Nothing is duplicated here. The import below pulls in the real content, so
.gemini/rules/project-rules.md stays the single place it is edited.
@./.gemini/rules/project-rules.md
Also binding
The universal, tool-independent rules live in AGENTS.md, and the
per-topic rules in .agents/rules/*.md. Read them when the task they
govern comes up — they are as binding here as they are for any other tool
this kit supports.
Why this file exists: this kit shipped a
.gemini/rules/project-rules.mdand an AI-tool table naming it as Gemini's source, but noGEMINI.mdanywhere and nocontext.fileNameoverride in a.gemini/settings.json— so Gemini CLI loaded none of it. Verified againstgeminicli.com/docs/cli/gemini-md. The alternative fix is a.gemini/settings.jsonwith{"context": {"fileName": ["GEMINI.md", "AGENTS.md"]}}; this file was chosen instead because it works with no configuration at all.
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.
- yesterday First seen · 30 lines · 362 tokens per session scan A 39ef62ecbb6d
code-intel GEMINI.md is an instructions file published in the GitHub repository SecondLifes/code-intel (2 stars, last pushed 21d ago), licensed Apache-2.0. It adds 362 tokens to every session, about $0.0018 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
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.