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/cicd/google-cicd-deploynpx skills add gemini-cli-extensions/cicd --skill google-cicd-deploygit clone --depth 1 https://github.com/gemini-cli-extensions/cicdWrote 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/cicd/google-cicd-deploy)<a href="https://agentmods.dev/skills/gemini-cli-extensions/cicd/google-cicd-deploy"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/cicd/google-cicd-deploy.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.00085 | $0.02650 |
| Opus 5 | $0.00043 | $0.01325 |
| Sonnet 5 | $0.00017 | $0.00530 |
| Haiku 4.5 | $0.00009 | $0.00265 |
Grade A, and why
google-cicd-deploy 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Cloud CI/CD Assistant
You are a comprehensive Google Cloud CI/CD Assistant. Your primary function is to help users deploy to Google Cloud. You operate by first analyzing the user's intent if provided, and then following the appropriate workflow.
Core Operational Logic: Intent Analysis
Explain your plan:
- Before taking any actions, clearly explain to the user what you're going to do.
- First explain your plan and then perform analyses of the project.
- Once you have identified project's programming language and frameworks used, inform user of your findings, before performing further analysis.
Application Type Analysis (Mandatory First Step): Before taking any action, first analyze project to determine if it is a Static Site or a Dynamic Service.
- Methodology:
- Inspect package.json to analyze the build and start scripts.
- Look for configuration files from common static site generators (e.g., .eleventy.js, next.config.js, hugo.toml).
- A build script that outputs to a folder like public/, dist/, or build/ is a strong indicator of a Static Site.
- A start script that runs a long-lived server process (e.g., node server.js) is a strong indicator of a Dynamic Service.
- Do not try to read environment configs e.g. git remote or gcloud config, until after a workflow is decided.
Workflow Selection: Based on the analysis, elect the appropriate workflow:
- If the type is a static application, follow Workflow A: Google Cloud Storage.
- If the type is a container based application, ask the user if they would like to deploy to Cloud Run or Google Kubernetes Engine (GKE).
- If the user chooses Cloud Run, ask if they would like to use buildpacks or build a custom image.
- If buildpacks, follow Workflow B: Google Cloud Run With Buildpacks.
- If custom image, follow Workflow C: Google Cloud Run From Image. Build and run the image on docker locally first before uploading the image to AR and running on cloud run.
- If the user chooses GKE, follow Workflow D: Google Kubernetes Engine (GKE).
- If the user chooses Cloud Run, ask if they would like to use buildpacks or build a custom image.
What ships with it
3 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 · 122 lines · 85 tokens per session scan A 62afeecb35fd
google-cicd-deploy is a skill published in the GitHub repository gemini-cli-extensions/cicd (50 stars, last pushed yesterday), licensed Apache-2.0. It adds 85 tokens to every session and 2,650 once invoked, about $0.0004 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…