bigquery-cost-check

bigquery-cost-check is a command for Claude Code from yeaight7/agent-powerups. It costs 19 tokens per session (285 once invoked), scanned A, original, Apache-2.0.

BigQuery SQL sorgularını veya dbt modellerini, çalıştırmadan önce veri tarama maliyeti açısından inceleyen bir komuttur. BigQuery, sorgulanan veri miktarına göre ücretlendiren bir bulut veri ambarıdır; dbt ise SQL dönüşümlerini yönetir.

In plain words
What is it for?
SQL sorgularındaki filtreleri ve seçilen sütunları incelemek; dbt yapılandırmasını kontrol etmek ve veri taramasını azaltacak öneriler hazırlamak için kullanılır.
Why use it?
Sorgu, ihtiyaçtan fazla tablo veya sütun tararsa gereksiz maliyet doğabilir. Komut, özellikle bölümleme alanlarının kullanılmaması ve büyük tabloların baştan oluşturulması gibi riskleri bulur.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the data-engineering plugin — 1 skill, 4 commands, 5 agents shipped together

Install

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.

agentmods
npx agentmods add commands/yeaight7/agent-powerups/bigquery-cost-check
Clone the repo
git clone --depth 1 https://github.com/yeaight7/agent-powerups

Made for: Claude Code.

Or install data-engineering, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 5 agents.

Wrote 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.

agentmods badge for bigquery-cost-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/yeaight7/agent-powerups/bigquery-cost-check.svg)](https://agentmods.dev/commands/yeaight7/agent-powerups/bigquery-cost-check)
Your own site
<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/bigquery-cost-check"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/bigquery-cost-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 285 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00285
Opus 5 $0.00010 $0.00143
Sonnet 5 $0.00004 $0.00057
Haiku 4.5 $0.00002 $0.00028

Measured 6d ago against content hash 3687d6d9337d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

bigquery-cost-check 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.

plugins/data-engineering/commands/bigquery-cost-check.md · 24 lines

What it actually says

BigQuery Cost Check Command

CRITICAL BEHAVIORAL RULES

  1. Analyze Static SQL: You cannot run the query to see the bytes billed. You must statically analyze the SQL syntax and dbt config() blocks.
  2. Focus on Bytes Billed: In BigQuery, cost is driven by data scanned, not compute time. Focus entirely on reducing data scanned.

Execution Steps

  1. Read the provided SQL or dbt model file.
  2. Look for the target table's schema (if available in the repo) to identify partitioned columns.
  3. Evaluate the WHERE clauses. Are partition keys used? If not, flag a full table scan.
  4. Evaluate the SELECT clauses. Are there unnecessary columns?
  5. For dbt models, check the config block. Is this a table, view, or incremental model? If it's a massive daily table rebuild, recommend an incremental strategy.
  6. Provide a concise report:
    • Risk Level: (Low, Medium, High)
    • Cost Drivers: (The specific lines or patterns driving cost)
    • Recommendations: (Specific SQL or config changes to implement)
Changes

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.

  1. 6d ago First seen · 24 lines · 19 tokens per session scan A 3687d6d9337d

Subscribe to this mod's changes

bigquery-cost-check is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 285 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.