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/data-agent-kit-starter-pack/bigquery-data-transfer-servicenpx skills add gemini-cli-extensions/data-agent-kit-starter-pack --skill bigquery-data-transfer-servicegit clone --depth 1 https://github.com/gemini-cli-extensions/data-agent-kit-starter-packWrote 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/data-agent-kit-starter-pack/bigquery-data-transfer-service)<a href="https://agentmods.dev/skills/gemini-cli-extensions/data-agent-kit-starter-pack/bigquery-data-transfer-service"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/data-agent-kit-starter-pack/bigquery-data-transfer-service.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.00079 | $0.01626 |
| Opus 5 | $0.00039 | $0.00813 |
| Sonnet 5 | $0.00016 | $0.00325 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
bigquery-data-transfer-service 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bigquery-data-transfer-service — 100% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BigQuery Data Transfer Service (DTS)
Mandatory Guidelines
[!IMPORTANT]
All new BigQuery Data Transfer Service (DTS) configurations MUST be provisioned through the gcp pipeline resource provisioning framework, which includes generating a
deployment.yaml.
- Do NOT use imperative CLI commands (e.g.,
bq mkorgcloud) to create or update configurations.- CLI commands are permitted only for discovery (listing/showing) and triggering manual runs.
This guide enables the discovery of existing ingestion resources and provides metadata related to ingestion when needed.
Workflow
Step 0: Discover Environment Parameters
Before generating configurations, discover the actual values for the target project and region.
[!TIP]
If
deployment.yamlalready exists in the repository root, prioritize extractingprojectandregionfrom the target environment configuration (e.g.,dev).
- Project:
gcloud config get project - Region:
gcloud config get compute/region
[!TIP]
Use these commands to replace placeholders like
<PROJECT_ID>with actual values. Always remove associated comments that start with TODO once replaced.
Step 1: Check for Existing Transfers
Before assuming a new transfer is needed, check for existing ones in the target region.
-
List Transfers:
bq ls --transfer_config \ --transfer_location=<REGION> \ --project_id=<PROJECT_ID> -
Analyze Existing Transfers:
-
Single Transfer Found:
- Check if the transfer has at least one successful run:
bq ls --transfer_run --transfer_config=<RESOURCE_NAME> - If found: Use existing transfer config.
- If not found: Confirm with user if it's ok to trigger the transfer run.
- Check if the transfer has at least one successful run:
-
Multiple Transfers Found:
- Attempt to guess the correct one based on context.
- Ask user to confirm.
-
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.
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.
- 6d ago First seen · 195 lines · 79 tokens per session scan A 8b34bf814948
bigquery-data-transfer-service is a skill published in the GitHub repository gemini-cli-extensions/data-agent-kit-starter-pack (179 stars, last pushed today), licensed Apache-2.0. It adds 79 tokens to every session and 1,626 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
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.