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 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/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/skills/gemini-cli-extensions/cicd/google-cicd-deploy"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/cicd/google-cicd-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00085 | $0.02650 |
| Opus 5.5 | $0.00034 | $0.01060 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (51 stars, last pushed today), licensed Apache-2.0. It adds 85 tokens to every session and 2,650 once invoked, about $0.0003 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 skills, from other repositories
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.