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/spe1977/cli-collaboration/gemini-mdgit clone --depth 1 https://github.com/Spe1977/cli-collaborationWhat 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.00779 | $0.00779 |
| Opus 5 | $0.00390 | $0.00390 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
cli-collaboration 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 2d 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.
This is a copy
92% identical to cli-collaboration CLAUDE.md — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEMINI.md
This project uses the cli-collaboration skill to coordinate Codex, Claude Code, Gemini CLI, Grok Build, and single-agent multi-session work on a shared repository.
Activation
When AGENT_HANDOFF.md exists at the project root, read it before any other file. Apply the cli-collaboration skill: declare the start gate, respect ### agent-owned, ### user-reserved, and ### frozen sections, and update the handoff last with files changed, tests, open concerns, and the next concrete step.
If AGENT_HANDOFF.md does not exist and the request involves a dirty worktree, work left by another CLI agent, or resume-from-previous-session intent, create the handoff in bootstrap mode (see skills/cli-collaboration/references/handoff-template.md, "Bootstrap variant") before any code change.
Start Gate
Before editing any file, state explicitly in your initial response, visible to the user:
- Handoff read: path and last-updated timestamp.
- Current task: one line.
- Files I will touch: explicit list, not directories.
- Expected red test: name, or "no test for this task" with the reason.
- Reserved zones confirmed: user-reserved and frozen areas read.
- Stop condition:
task-complete|context-budget|blocker.
If you cannot fill one of those fields, read more or ask the user. Do not improvise.
Ownership
Never edit a file listed under ### user-reserved or ### frozen without explicit user approval. For ### agent-owned files, edit only those assigned to Gemini. If the request requires touching a file owned by Codex, Claude, or another agent, stop, name the file and owner, and ask for reassignment or deferment.
When in doubt, run:
skills/cli-collaboration/scripts/check-ownership.sh --agent Gemini <file...>
Exit 0 = no conflict, 1 = ownership conflict, 2 = malformed handoff.
Destructive Actions
Never run or recommend without explicit user approval:
git reset --hardgit cleangit stash(unauthorized)git restore(on files not authored in this shift)git checkout --(on files not authored in this shift)- lateral overwrite of files authored by another agent or the user
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.
- 2d ago First seen · 80 lines · 779 tokens per session scan A 558e9607ccdf
cli-collaboration GEMINI.md is an instructions file published in the GitHub repository Spe1977/cli-collaboration (3 stars, last pushed 1mo ago), licensed MIT. It adds 779 tokens to every session, about $0.0039 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to cli-collaboration CLAUDE.md, differing in 12 lines, and is treated as a copy.
Other instructions, from other repositories
adk-go AGENTS.md
AGENTS.md instructions for google/adk-go, covering agents.md, project overview, skills, setup & core commands and definition of done.
cli CLAUDE.md
Claude Code instructions for entireio/cli, covering entire - cli, architecture, key directories, commands (cmd/) and command layout.
cli copilot-instructions.md
Copilot instructions for entireio/cli, covering copilot instructions for entire cli, repository overview, build & validation commands, critical code patterns and error handling.
adk-go CLAUDE.md
Claude Code instructions for google/adk-go: See AGENTS.md for project context, commands, and contribution guidelines for AI coding agents.
agent-starter-pack GEMINI.md
Instructions for GoogleCloudPlatform/agent-starter-pack, covering agent starter pack - ai coding agent guide, core principles for ai agents, project architecture overview, 4-layer template system and key directory structure.
codedb AGENTS.md
AGENTS.md instructions for justrach/codedb, covering codedb agent guidelines, what codedb is (and isn't), review guidelines, pre-merge verification and security-sensitive areas.