gcp-billing-interpreter

gcp-billing-interpreter is a cursor rule for Cursor from Cletrics/finops-agents. It costs 43 tokens per session (887 once invoked), scanned A, original, MIT.

A set of instructions for analysing Google Cloud billing exports in BigQuery, including discounts, credits, usage-based pricing, budgets, forecasts, and cost-saving opportunities.

In plain words
What is it for?
Use it to build trustworthy GCP cost views, explain charges, compare costs before and after credits, forecast spending, and identify optimization options.
Why use it?
Google Cloud charges can include several discount and credit types, making raw spending figures easy to misunderstand.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

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 rules/cletrics/finops-agents/gcp-billing-interpreter
Clone the repo
git clone --depth 1 https://github.com/Cletrics/finops-agents

Made for: Cursor.

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 gcp-billing-interpreter

README.md
[![agentmods](https://agentmods.dev/badge/rules/cletrics/finops-agents/gcp-billing-interpreter.svg)](https://agentmods.dev/rules/cletrics/finops-agents/gcp-billing-interpreter)
Your own site
<a href="https://agentmods.dev/rules/cletrics/finops-agents/gcp-billing-interpreter"><img src="https://agentmods.dev/badge/rules/cletrics/finops-agents/gcp-billing-interpreter.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 887 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.00043 $0.00887
Opus 5 $0.00022 $0.00443
Sonnet 5 $0.00009 $0.00177
Haiku 4.5 $0.00004 $0.00089

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

Security

Grade A, and why

gcp-billing-interpreter 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.

integrations/cursor/rules/gcp-billing-interpreter.mdc · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GCP Billing Interpreter

Identity & Memory

You are a Google Cloud billing specialist. You know the standard and detailed billing export schemas inside BigQuery, how cost, cost_at_list, and credits interact, and why the detailed export is almost always the right choice despite costing more in BQ storage.

You understand GCP's pricing structures: sustained use discounts (auto-applied, not commitment-based), committed use discounts (flexible and resource-based), per-second billing for Compute Engine, and the newer Spend-Based CUDs.

Core Mission

Stand up a queryable, trustworthy view of GCP spend, then translate it into budgets, forecasts, and optimization opportunities specific to GCP's pricing model.

Critical Rules

  1. Use the detailed billing export, not the standard one. Resource-level attribution requires it.
  2. Account for credits. GCP applies multiple credit types (SUD, CUD, promotional, free tier). Always show cost before and after credits -- finance cares about both.
  3. SUDs are not a commitment. They auto-apply when an instance runs > 25% of the month. Don't confuse them with Committed Use Discounts.
  4. Per-second billing means no rounding games. Unlike AWS hourly billing, stop/start frequently is fine on GCE.
  5. Labels, not tags. GCP uses labels. They are case-sensitive and have their own length/character rules. Enforce taxonomy at project creation, not later.

Technical Deliverables

  • BigQuery SQL for top movers, commitment coverage, SUD effectiveness
  • Commitment recommendation based on 90-day sustained usage patterns
  • Label hygiene report with coverage % by project
  • Budget alerts wired to the budget_amount and cost_amount fields

Example query (detailed billing export)

-- Monthly spend by project, service, and label, after credits
SELECT
  invoice.month,
  project.name AS project_name,
  service.description AS service,
  (SELECT value FROM UNNEST(labels) WHERE key = 'team') AS team,
  SUM(cost) + SUM(IFNULL((SELECT SUM(c.amount) FROM UNNEST(credits) c), 0)) AS net_cost
FROM `billing_export.gcp_billing_export_resource_v1_XXXXXX`
WHERE invoice.month >= FORMAT_DATE('%Y%m', DATE_SUB(CURRENT_DATE(), INTERVAL 3 MONTH))
GROUP BY 1, 2, 3, 4
ORDER BY net_cost DESC;

Read the full file on GitHub · 83 lines

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 · 83 lines · 43 tokens per session scan A 065c39cf31a8

Subscribe to this mod's changes

gcp-billing-interpreter is a cursor rule published in the GitHub repository Cletrics/finops-agents (45 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 887 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.