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-release-orchestrationgit 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-release-orchestration)<a href="https://agentmods.dev/skills/gemini-cli-extensions/cicd/google-cicd-release-orchestration"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/cicd/google-cicd-release-orchestration.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.1 | $0.00082 | $0.02447 |
| Opus 5 | $0.00041 | $0.01223 |
| Sonnet 5 | $0.00016 | $0.00489 |
| Haiku 4.5 | $0.00008 | $0.00245 |
Grade A, and why
google-cicd-release-orchestration 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 7d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Deploy Pipelines
Overview
This skill encompasses the entire lifecycle of Cloud Deploy for a user, from designing and creating delivery pipelines to managing releases and debugging release failures.
All Workflows require the clouddeploy.googleapis.com API to be enabled.
Workflow: Designing a Pipeline
This workflow provides steps for designing a Cloud Deploy DeliveryPipeline.
Constraints & Rules
- NO PLACEHOLDERS: Never generate YAML with placeholders like
<PROJECT_ID>. Ask the user for values first. - Context First: Always check existing files and conversation context before asking.
- Step-by-Step: Perform the steps one at a time. The goal is to guide the user through designing a delivery pipeline.
Step 0: Prerequisites
Required Context: Before generating ANY configuration for this workflow, you MUST have the following values. Ask the user strictly for any missing information:
- Project ID: The Google Cloud project ID for the Cloud Deploy resources.
- Region: The region for the Cloud Deploy resources (e.g.,
us-central1). - Application Name: The name of the application that will be deployed. Use the application name to generate the names of the Cloud Deploy resources, such as
DeliveryPipelineandTargetresources. - Runtime: Either Cloud Run or Google Kubernetes Engine (GKE).
- If Cloud Run: The Cloud Run project and location.
- If GKE: The GKE cluster name.
Step 1: Define the target environments
- Identify the number of deployment environments (e.g., dev, staging, production).
- Identify if promotions should require user approval.
- Define each of the deployment environments as Cloud Deploy
Targetresources in aclouddeploy.yamlfile.- Use
references/configure-targets.mdas a reference when generating the resource YAML. - Always prefix target IDs with the application name provided by the user (e.g.,
[app-name]-[env]) to prevent resource name collisions when multiple applications are deployed to different environments. For example, if the user wants to deploy an application named "hello-world" to test and prod environments, then use "hello-world-test" and "hello-world-prod" as theTargetIDs.
- Use
What ships with it
8 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.
- references/basic-cloudrun-alerts.md 3.2 KB
- references/basic-cloudrun-manifests.md 1.0 KB
- references/basic-k8s-manifests.md 1.2 KB
- references/configure-automations.md 4.6 KB
- references/configure-pipelines.md 5.3 KB
- references/configure-skaffold.md 2.8 KB
- references/configure-targets.md 1.5 KB
- references/iam-permissions.md 1.5 KB
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.
- 7d ago First seen · 197 lines · 82 tokens per session scan A ff0c8b146f79
google-cicd-release-orchestration is a skill published in the GitHub repository gemini-cli-extensions/cicd (50 stars, last pushed yesterday), licensed Apache-2.0. It adds 82 tokens to every session and 2,447 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
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-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.
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-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.