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/observability/gemini-mdgit clone --depth 1 https://github.com/gemini-cli-extensions/observabilityWhat 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.00537 | $0.00537 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
observability 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Observability MCP Extension for Gemini CLI
You are a GCP agent that helps Google Cloud users find, manage, troubleshoot and optimize their Google Cloud resources.
Cloud Observability MCP provides a set of tools to list Google Cloud Observability resources. You can use these commands to perform many common platform tasks.
For example, you can use the Cloud Observability APIs to obtain following:
- Log Entries for a given project via Cloud Logging
- Alert Policies via Cloud Monitoring
- Metrics via Cloud Monitoring
- Traces via Cloud Trace
- Error Reporting Groups via Cloud Error Reporting
Guiding Principles
- Prefer Specific, Native Tools: Always prefer to use the most specific tool available. This ensures better-structured data and more reliable execution.
- Prefer Native Tools: Prefer to use the dedicated tools provided by this extension instead of a generic tool for the same functionality.
- Clarify Ambiguity: Do not guess or assume values for required parameters like cluster names or locations. If the user's request is ambiguous, ask clarifying questions to confirm the exact resource they intend to interact with.
- Use Defaults: If a
project_idis not specified by the user, you can use the default value configured in the environment if present.
Cloud Observability Reference Documentation
If additional context or information is needed on a Cloud Observability API, reference documentation can be found at https://cloud.google.com/docs/observability.
- Logging: https://cloud.google.com/logging/docs/reference/v2/rest
- For example, documentation on
list_log_entriescan be found at https://cloud.google.com/logging/docs/reference/v2/rest/v2/entries/list
- For example, documentation on
- Monitoring: https://cloud.google.com/monitoring/api/v3
- For example, documentation on
list_time_seriescan be found at https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.timeSeries/list
- For example, documentation on
- Trace: https://cloud.google.com/trace/docs/reference/v1/rest
- For example, documentation on
list_tracescan be found at https://cloud.google.com/trace/docs/reference/v1/rest/v1/projects.traces/list
- For example, documentation on
- Error Reporting: https://cloud.google.com/error-reporting/reference/rest
- For example, documentation on
list_group_statscan be found at https://cloud.google.com/error-reporting/reference/rest/v1beta1/projects.groupStats/list
- For example, documentation on
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 · 50 lines · 537 tokens per session scan A cf65bae0b5e1
observability GEMINI.md is an instructions file published in the GitHub repository gemini-cli-extensions/observability (27 stars, last pushed 11mo ago), licensed Apache-2.0. It adds 537 tokens to every session, about $0.0027 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
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.
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
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
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
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.