Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/looker-open-source/looker-skillsnpx agentmods add skills/looker-open-source/looker-skills/connecting-looker-to-bigqueryWrote 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/looker-open-source/looker-skills/connecting-looker-to-bigquery)<a href="https://agentmods.dev/skills/looker-open-source/looker-skills/connecting-looker-to-bigquery"><img src="https://agentmods.dev/badge/skills/looker-open-source/looker-skills/connecting-looker-to-bigquery/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/looker-open-source/looker-skills/connecting-looker-to-bigquery"><img src="https://agentmods.dev/badge/skills/looker-open-source/looker-skills/connecting-looker-to-bigquery.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.00048 | $0.01054 |
| Opus 5 | $0.00024 | $0.00527 |
| Sonnet 5 | $0.00010 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
connecting-looker-to-bigquery 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 12d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connecting Looker to BigQuery
Creates a database connection in Looker to Google BigQuery. This instruction uses Application Default Credentials (ADC), which is the recommended and most secure method for Looker Core instances running in Google Cloud, as it avoids managing service account keys.
Prerequisites
- Looker CLI must be installed and authenticated (see
installing-looker-cliandauthenticating-looker-cliskills). - Looker Core instance service account must have the necessary IAM roles on the BigQuery project.
Instructions
1. Identify the GCP Project and Datasets
Identify the following parameters from Step 1 (Discovery):
- GCP Project ID: The GCP project containing the BigQuery datasets (allows hyphens).
- Dataset ID: The BigQuery dataset you want to explore (must be alphanumeric/underscores only, no hyphens).
2. Pre-flight Check: Looker Service Account IAM Roles
Verify that the Looker Core service account has the necessary IAM roles on the
target GCP project (BigQuery Data Viewer, BigQuery Job User, and Service Usage Consumer):
[!IMPORTANT] When running queries through the BigQuery connection from the Looker instance, Google Cloud requires the Looker service account to have permission to compute/use resources within the project where BigQuery is billed. Without the
roles/serviceusage.serviceUsageConsumerrole (which containsserviceusage.services.use), Looker cannot authenticate or dispatch query jobs to BigQuery, resulting in a400 Bad Requesterror.
-
Run the IAM pre-flight check script, passing the Looker GCP project ID (where the Looker Core instance resides) and the BigQuery GCP project ID:
./skills/onboarding-preflight-check/scripts/preflight_check.sh \ --mode iam \ --looker-project {looker_gcp_project_id} \ --bq-project {bigquery_gcp_project_id} -
If the check fails because roles are missing, first obtain the Looker GCP project number (or copy the exact service account email from the preflight check error output):
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.
- 12d ago First seen · 123 lines · 48 tokens per session scan A 6248b3857f84
connecting-looker-to-bigquery is a skill published in the GitHub repository looker-open-source/looker-skills (28 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,054 once invoked, about $0.0002 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.