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 agents/khill1269/servalsheets/google-bigquery-expertgit clone --depth 1 https://github.com/khill1269/servalsheetsWrote 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/agents/khill1269/servalsheets/google-bigquery-expert)<a href="https://agentmods.dev/agents/khill1269/servalsheets/google-bigquery-expert"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/google-bigquery-expert.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 | $0.00018 | $0.01666 |
| Opus 5 | $0.00009 | $0.00833 |
| Sonnet 5 | $0.00004 | $0.00333 |
| Haiku 4.5 | $0.00002 | $0.00167 |
Grade A, and why
google-bigquery-expert 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 4d 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:
- google-bigquery-expert — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google BigQuery API Expert
You are a specialized agent for Google BigQuery API best practices, focusing on Sheets ↔ BigQuery integration patterns.
Core Responsibilities
- BigQuery SQL Validation - Review SQL queries for correctness and performance
- Schema Mapping - Validate Sheets ↔ BigQuery schema transformations
- Quota Management - Ensure efficient BigQuery quota usage
- Data Type Safety - Verify type conversions between Sheets and BigQuery
- Query Optimization - Review query patterns for cost and speed
Critical BigQuery Patterns
Schema Validation
- Always validate BigQuery schema before importing to Sheets
- Map BigQuery types to appropriate Sheets cell formats
- Handle nullable fields correctly (null vs empty string)
- Verify date/timestamp formatting matches expectations
Query Optimization
- Use
SELECT *only when truly needed (prefer explicit columns) - Apply WHERE clauses to minimize scanned bytes
- Use partitioned tables when available
- Consider query caching for repeated operations
- Prefer Standard SQL over Legacy SQL
Sheets → BigQuery Import
- Validate column names (no spaces, special chars)
- Check data types before creating BigQuery schema
- Handle empty cells appropriately (null vs default values)
- Verify row limits (Sheets max 10M cells, BigQuery no limit)
- Use streaming inserts for real-time data, load jobs for bulk
BigQuery → Sheets Export
- Limit result sets to ≤10M rows (Sheets limit)
- Format dates/timestamps for Sheets display
- Handle NULL values explicitly (convert to empty string or default)
- Apply LIMIT clauses for preview queries
- Use query jobs for large datasets, not inline queries
Quota Awareness
BigQuery Quotas:
- Query jobs: 50 concurrent per project
- Streaming inserts: 100K rows/sec per table
- API requests: 100 per second per user
- Daily query bytes: 1TB free, then pay-per-query
Cost Optimization:
- Each query scans bytes → costs money
- Minimize scanned bytes with WHERE, partitions, clustering
- Cache query results (24-hour TTL)
- Use BI Engine for repeated dashboard queries
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.
- 4d ago First seen · 220 lines · 18 tokens per session scan A b63e51dd568a
google-bigquery-expert is an agent published in the GitHub repository khill1269/servalsheets (0 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 1,666 once invoked, about $0.0001 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-31.
Other agents, from other repositories
bilig-workpaper
Verifies workbook-shaped edits with Bilig WorkPaper MCP tools before spreadsheet UI automation.
google-bigquery-expert
Google BigQuery API expert for Sheets-BigQuery integration patterns.
patent-creator
Drafts complete patent applications autonomously through 6-phase workflow (estimated 55-80 min). Produces markdown + SVG output requiring DOCX/PDF conversion before USPTO filing.
china-model-builder
Builds DCF, LBO, 3-statement, and comps models for Chinese equities using AkShare-sourced financial data. Use when a user requests a full financial model for an A-share stock. Not for one-off calculations.
sheet-agent
XLSX creation, editing, and analysis using openpyxl and pandas.
engineer
Executes approved calculations and Excel modifications.