gcp-pipeline-resource-provisioning

gcp-pipeline-resource-provisioning is a skill for Claude Code, Codex from saski/arnesto. It costs 191 tokens per session (1,485 once invoked), scanned A, a copy of gcp-pipeline-resource-provisioning, Unlicense.

A workflow for defining and deploying Google Cloud resources used by data pipelines through a shared deployment.yaml file. It covers services such as BigQuery, Dataform, Dataproc, and BigQuery Data Transfer Service.

In plain words
What is it for?
Use it to create or update pipeline resources declaratively, then deploy the definitions for the required environment.
Why use it?
It keeps resource definitions and environment settings together for development, staging, and production. It also requires labels and destination details needed for tracking and data-transfer setup.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to create or update pipeline resources declaratively, then deploy the definitions for the required environment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/saski/arnesto/gcp-pipeline-resource-provisioning
Install

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.

Any agent
npx skills add saski/arnesto --skill gcp-pipeline-resource-provisioning
Clone the repo
git clone --depth 1 https://github.com/saski/arnesto

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for gcp-pipeline-resource-provisioning

README.md
[![agentmods](https://agentmods.dev/badge/skills/saski/arnesto/gcp-pipeline-resource-provisioning/github.svg)](https://agentmods.dev/skills/saski/arnesto/gcp-pipeline-resource-provisioning)
Your own site
<a href="https://agentmods.dev/skills/saski/arnesto/gcp-pipeline-resource-provisioning"><img src="https://agentmods.dev/badge/skills/saski/arnesto/gcp-pipeline-resource-provisioning/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.

agentmods 80×15 button for gcp-pipeline-resource-provisioning

Your own site · 80×15
<a href="https://agentmods.dev/skills/saski/arnesto/gcp-pipeline-resource-provisioning"><img src="https://agentmods.dev/badge/skills/saski/arnesto/gcp-pipeline-resource-provisioning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 191 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,485 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00191 $0.01485
Opus 5 $0.00096 $0.00743
Sonnet 5 $0.00038 $0.00297
Haiku 4.5 $0.00019 $0.00148

Measured 11d ago against content hash 375d3a13d9fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

gcp-pipeline-resource-provisioning 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 11d 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.

Origin

This is a copy

100% identical to gcp-pipeline-resource-provisioning — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/gcp-pipeline-resource-provisioning/SKILL.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

How to use this skill

Create or update existing deployment.yaml file and deploy resources. All configuration files MUST be maintained together in the repository root.

Mandatory labels

[!IMPORTANT]

Whenever you generate resource definitions in deployment.yaml, you MUST directly populate the datacloud label under definition.labels for every resource to track the source of creation. Determine the value based on your current IDE environment:

  • For Antigravity, set datacloud: "antigravity"
  • For VS Code, set datacloud: "vscode"
  • For any other environment, set datacloud: "other"

Do not use a variable substitution for this label; hardcode the appropriate string value directly into each resource definition (e.g., replacing __REQUIRED_LABEL__ placeholders).

Special rule for BigQuery DTS Ingestion: Whenever you generate a bigquerydatatransfer.transferConfig in deployment.yaml, you MUST also explicitly define its target destination bigquery.dataset in the same file and apply the datacloud label to it. You must do this even if the dataset already exists, to ensure the destination dataset's labels are patched and updated.

Step 1: Supported Resource Types

The framework supports deploying various GCP resources. To see the comprehensive list of supported resource types, run the following command:

gcloud beta orchestration-pipelines resource-types list

Refer to: references/gcp-pipeline-resource-provisioning_spec.md to understand the template for deployment.yaml.

Step 2: Discover Environment Parameters

Before generating configurations, discover the actual values for the target project, region, environment, and commit SHA.

[!TIP]

If deployment.yaml already exists in the repository root, prioritize extracting project and region from the target environment configuration (e.g., dev).

  1. Project ID:

    gcloud config get project
    

Read the full file on GitHub · 172 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 11d ago First seen · 172 lines · 191 tokens per session scan A 375d3a13d9fa

Subscribe to this mod's changes

gcp-pipeline-resource-provisioning is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed yesterday), licensed Unlicense. It adds 191 tokens to every session and 1,485 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gcp-pipeline-resource-provisioning, differing in 0 lines, and is treated as a copy.