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 skills/gemini-cli-extensions/sre/gcp-setupnpx skills add gemini-cli-extensions/sre --skill gcp-setupgit clone --depth 1 https://github.com/gemini-cli-extensions/sreWrote 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/skills/gemini-cli-extensions/sre/gcp-setup)<a href="https://agentmods.dev/skills/gemini-cli-extensions/sre/gcp-setup"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/sre/gcp-setup.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00397 |
| Opus 5 | $0.00018 | $0.00198 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
gcp-setup 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 4d 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
GCP Environment Setup
Use this skill to verify and harmonize your GCP identities at the start of an investigation or session.
Core Workflow
- Identity Verification: Run the bundled
gcp-whoami.shscript to check all three major identities (gcloud, ADC, and kubectl). - Harmonization: If identities mismatch, offer to fix them.
- To fix
gcloud:gcloud auth login [ACCOUNT] - To fix ADC:
gcloud auth application-default login - To fix GKE/kubectl:
gcloud container clusters get-credentials [CLUSTER] --region [REGION] --project [PROJECT]
- To fix
- Next Step: Architecture Discovery(Optional): Once identities are verified and correct, check if the
./discover/{gcp-project|azure-subscription}/{PROJECT_ID_OR_NAME}directory exists. If it is missing or empty, and user asked transition to thegcp-architecture-discoveryskill and explicitly instruct it to execute a full baseline discovery to sweep and map the entire infrastructure state.
Bundled Scripts
scripts/gcp-whoami.sh: Displays current identities for gcloud, ADC, and kubectl.
Safe Mode Support
If SAFE_MODE="enabled" is found in the environment or .env file, you MUST activate the safe-sre-investigator skill immediately after verifying the initial setup. This ensures all subsequent operations use read-only/non-mutating service accounts.
Note that the SAFE_MODE might impact kubectl authorization via RBAC.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 31 lines · 36 tokens per session scan A cab34e415003
gcp-setup is a skill published in the GitHub repository gemini-cli-extensions/sre (83 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 397 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…