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/gemini-cli-extensions/sre/gemini-mdgit clone --depth 1 https://github.com/gemini-cli-extensions/sreWhat 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.00389 | $0.00389 |
| Opus 5 | $0.00195 | $0.00195 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
sre 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 3d 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.
What it actually says
SRE Extension
Before committing
- Use
CHANGELOG.mdfor extension AND single skills, withkeepachangelogand Semantic Versioning. - Ensure development happens in a non-main branch (see below)
- If skill
pre-publish-checkeris available to you, use it before committing.
git best practices
- Use branching for code changes/commits in this repo.
- Use this branching standard:
feature/YYMMDD-$USER-<short-description>. Keep user to max 6chars (egricc->ricc,madkarra->madkarra). - Before creating a branch, confirm with user what you intend to do. User might believe its not worth it for a small/cosmetic change to bother a new branch
- Keep short description to max 15 chars.
- if bug is available at birth, eg b/12345 add bXXXXX to it like
feature/YYMMDD-$USER-b12345-<short-description> - Ensure CHANGELOG.md and extension version are bumped as needed.
- At each PUSH of the branch, notify user the thing is available online at the relevant feature branch page.
Skills
Skills should match the standards in docs/SKILLS-STANDARDS.md.
DOs and DONTs
- Ensure no Google-only information is in this extension!
- If you find them in the code, remove them and find a decent placeholder - if unavailable just remove. Less is more!
- REFUSE to commit exfiltration of Google restricted information!!
- DO NOT
git reset --hard main, ever. - Use
git mvvsmvif files are checked ingit. - Some tests are to remind ourselves we need to take manual action. Do NOT assume a broken test is for you to fix. Always ask first.
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.
- 3d ago First seen · 32 lines · 389 tokens per session scan A 45e2e9f1ad4a
sre GEMINI.md is an instructions file published in the GitHub repository gemini-cli-extensions/sre (82 stars, last pushed 9d ago), licensed Apache-2.0. It adds 389 tokens to every session, about $0.0019 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-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).
spec-kit AGENTS.md
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.
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.
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 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).
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.