Borrowing it
Nothing to install: this file belongs to rexleimo/aios. 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/rexleimo/aios/main/GEMINI.mdgit clone --depth 1 https://github.com/rexleimo/aiosWrote 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/rexleimo/aios/gemini-md)<a href="https://agentmods.dev/instructions/rexleimo/aios/gemini-md"><img src="https://agentmods.dev/badge/instructions/rexleimo/aios/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/rexleimo/aios/gemini-md"><img src="https://agentmods.dev/badge/instructions/rexleimo/aios/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.01833 | $0.01833 |
| Opus 5.5 | $0.00733 | $0.00733 |
| Sonnet 5.5 | $0.00367 | $0.00367 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
aios 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tools: code-review-graph
This project exposes a structural knowledge graph via the code-review-graph MCP. Use it only when structural relationships materially affect the current decision; do not turn routine work into a graph-tool loop.
Bounded checkpoints
- Initial orientation: call
get_minimal_context(task="...")at most once when repository structure is not already clear. - Before a risky or multi-file change: use
get_impact_radius(detail_level="minimal"); callquery_graph(pattern="tests_for", target="...")only for the concrete target being changed. - After edits: call
detect_changes(detail_level="minimal")once when the graph was used or the change has meaningful blast radius. - Before submitting: use
get_affected_flows()orget_suggested_questions()only if unresolved structural risk remains. - Finding code: prefer
semantic_search_nodeswhen semantic graph search is likely to beat a direct repository search. - Budget: no more than three graph calls per work item. Treat
next_tool_suggestionsas optional hints and never follow them recursively.
Planning context proposals
When an active structured-plan task has implementation targets, call AIOS MCP aios_plan_task with action="propose_context", the task id, and workspace-relative targets when the task has none. The tool derives target, caller, callee, and test candidates from codemap, but it does not modify the active plan. Present the candidate refs to a human. An explicit human-controlled CLI confirmation with aios plan task <id> --confirm-context-candidates (optionally repeated --candidate-ref <ref>) activates selected refs for orchestration; it is a process boundary, not an identity/authentication boundary. Do not claim context will be delivered before that command succeeds.
Memory Trigger Contract (记忆触发契约)
Gemini CLI 没有 hook 面：记忆召回完全由 agent 主动触发。
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 Changed · +2 lines · +41 tokens per session e6b2c29600da
- 1mo ago Changed · +45 lines · +654 tokens per session f3fdefc7c2b0
- 1mo ago First seen · 94 lines · 1,138 tokens per session scan A dda0986d80a8
aios GEMINI.md is an instructions file published in the GitHub repository rexleimo/aios (61 stars, last pushed today), licensed MIT. It adds 1,833 tokens to every session, about $0.0073 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.