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-bigframesnpx skills add gemini-cli-extensions/data-agent-kit-starter-pack --skill bigquery-bigframesgit clone --depth 1 https://github.com/gemini-cli-extensions/data-agent-kit-starter-packWhat 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 | $0.00076 | $0.01193 |
| Opus 5 | $0.00038 | $0.00596 |
| Sonnet 5 | $0.00015 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00119 |
Grade A, and why
bigquery-bigframes 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 2d 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.
This is a copy
97% identical to bigquery-bigframes — 3 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BigFrames (BigQuery DataFrame) basics
BigFrames is a Python library that lets you take advantage of BigQuery data processing by using familiar Python APIs.
Dataframe API best practices
- Stay in the Cloud: Perform data cleaning, transformation, and analysis via BigFrames methods to leverage BigQuery's scale rather than downloading data.
- Prefer partial ordering mode: Enable partial ordering mode right after
importing BigFrames. This speeds up data processing significantly by relaxing
row-sequence constraints.
import bigframes.pandas as bpd bpd.options.bigquery.ordering_mode = 'partial' - Use
peek()for data preview: Usepeek(n)to preview data instead ofhead(n).peek(n)randomly samplesnrows and is significantly faster.head(n)returns rows in strict order and fails inpartialordering mode unless the DataFrame has been explicitly sorted. - Avoid materializing data locally: Methods like
to_pandas()download all data to client memory, bypassing BigQuery’s distributed computation and risking Out of Memory (OOM) errors. Do not materialize data locally unless:- The dataset is small enough to fit safely in memory.
- An error message explicitly requires local materialization.
- Prefer Dataframe API over SQL queries: Do not write raw SQL queries via
read_gbq()if a DataFrame/Series method achieves the same result, as it breaks the Pandas abstraction and prevents lazy query execution. - Accessors over UDFs/Lambdas:
- Use built-in accessors (e.g.,
df.col.str.*,df.col.dt.*) instead of remote User Defined Functions (UDFs). UDFs require extra resources and time to deploy. - Do not use lambdas with
Series.map()orDataFrame.apply(). These methods do not accept functions withoutudforremote_functiondecorators.
# Avoid: df["upper"] = df["name"].map(lambda x: x.upper()) # Prefer: df["upper"] = df["name"].str.upper() - Use built-in accessors (e.g.,
- Schema Verification: Do not assume the schema of intermediate outputs.
Proactively verify schemas using
.dtypesand inspect sample records usingdisplay()with.peek(). - Visualization: Plot directly from the BigFrames DataFrame/Series when
possible. BigFrames is compatible with Matplotlib and Seaborn. If direct
plotting fails, use the
.plotaccessor. If the dataset is too large to plot, aggregate or sample the data before calling.to_pandas()to plot locally.
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.
- 2d ago First seen · 100 lines · 76 tokens per session scan A 1f736d9a558d
bigquery-bigframes is a skill published in the GitHub repository gemini-cli-extensions/data-agent-kit-starter-pack (177 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 1,193 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to bigquery-bigframes, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.