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 skills add withoneai/one-agent-plugin --skill bigquerygit clone --depth 1 https://github.com/withoneai/one-agent-pluginWrote 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/withoneai/one-agent-plugin/bigquery)<a href="https://agentmods.dev/skills/withoneai/one-agent-plugin/bigquery"><img src="https://agentmods.dev/badge/skills/withoneai/one-agent-plugin/bigquery.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.00103 | $0.03857 |
| Opus 5 | $0.00051 | $0.01929 |
| Sonnet 5 | $0.00021 | $0.00771 |
| Haiku 4.5 | $0.00010 | $0.00386 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BigQuery through One
BigQuery is a serverless, highly scalable, and cost-effective data warehouse designed for running fast SQL queries on large datasets. It enables businesses to analyze data quickly and make informed decisions.
One exposes BigQuery through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.
How to run an action
- Find the action in the table below, or call
search_one_platform_actionswith platformbigqueryif it is not listed. - Call
get_one_action_knowledgewith the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters. - Call
execute_one_actionwith parameters copied from that knowledge.
Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.
Before you start
Call list_one_integrations once and confirm BigQuery is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.
Each connection carries an access field. If it reports {"policy": "methods", "methods": ["GET"]} the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.
Before a write
Creates, updates, deletes and sends land on a real BigQuery account and cannot be recalled. State the action and the specific target in one line before the first write in a task, and let the user stop you. Reads need no confirmation.
Actions
Routines
| Action | Method | Path | Action id |
|---|---|---|---|
| Get a Dataset Routine | GET | /bigquery/v2/projects/{{projectId}}/datasets/{{datasetId}}/routines/{{routineId}} |
conn_mod_def::GJ6RWiUxNOw::JF9a1HqoQZmA0dkO_8K-Tw |
| List a Dataset's Routines | GET | /bigquery/v2/projects/{{projectId}}/datasets/{{datasetId}}/routines |
conn_mod_def::GJ6RWjIH6aQ::83ChQuEPTn21glsXG0cZ_g |
| Create a Dataset Routine | POST | /bigquery/v2/projects/{{projectId}}/datasets/{{datasetId}}/routines |
conn_mod_def::GJ6RWl1QXeQ::Zh23Fy03TpSYbYAvz-5MqA |
| Delete a Dataset Routine | DELETE | /bigquery/v2/projects/{{projectId}}/datasets/{{datasetId}}/routines/{{routineId}} |
conn_mod_def::GJ6RWgD9qNk::Byeq8dOaQuW3JKPAlsTRHQ |
| Get a Routine's IAM Policy | POST | /bigquery/v2/{{resource}}:getIamPolicy |
conn_mod_def::GJ6RWiW7NKc::EMHmDdU-RU6LrxCzEc53dg |
| Set IAM Policy for a BigQuery Routine | POST | /bigquery/v2/{{resource}}:setIamPolicy |
conn_mod_def::GJ6RWuruqyw::sp-7ibWrT0asrJkaJcOtLw |
| Test IAM Permissions for a BigQuery Routine | POST | /bigquery/v2/{{resource}}:testIamPermissions |
conn_mod_def::GJ6RWupbyZM::IlSH9n06TAqzy4oHJ-IKsg |
| Update a Dataset Routine | PUT | /bigquery/v2/projects/{{projectId}}/datasets/{{datasetId}}/routines/{{routineId}} |
conn_mod_def::GJ6RWv__y0o::zCBbwdnpS6aoSxiA2BlHXg |
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 · 157 lines · 0 tokens per session scan A 170e61211a72
bigquery is a skill published in the GitHub repository withoneai/one-agent-plugin (1 stars, last pushed 18d ago), licensed MIT. It adds 103 tokens to every session and 3,857 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
cargo-storage
Work with the data inside a Cargo workspace — models (Companies, Contacts, Deals…), datasets, columns, relationships, records, and SQL over workspace storage. Triggers: "what models do I have", "show me the schema", "add a column for", "how many contacts do I have", "SELECT … FROM", "query my companies table", "join…
writing-sql
Write SQL queries for Celigo RDBMS exports and imports -- SELECT, INSERT, UPDATE, UPSERT, MERGE, delta, once, and bulk operations across Snowflake, Postgres, MySQL, SQL Server, Oracle, BigQuery, and Redshift. Use when editing rdbms.query or troubleshooting SQL errors.
configuring-lookup-caches
Configure Celigo lookup cache resources -- in-memory key-value stores used for fast lookups, deduplication, cross-reference resolution, and state tracking during flow execution. Use when creating caches, loading data, referencing caches in import lookups, or managing cache lifecycle.
vector-database-engineer
Skill "vector-database-engineer" from frank-luongt/faos-skills-marketplace, covering vector database engineer, do not use this skill when, instructions, capabilities and use this skill when.
supabase
Manage Supabase projects from the command line. Query tables, insert/update/delete rows, manage RLS policies, handle auth users, and work with storage. Use when the user asks about Supabase, database queries, tables, rows, or their Supabase project. Triggers on: "query supabase", "show me the table", "insert into"…