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 rules/cletrics/finops-agents/gcp-billing-interpretergit clone --depth 1 https://github.com/Cletrics/finops-agentsWrote 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/rules/cletrics/finops-agents/gcp-billing-interpreter)<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>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.00043 | $0.00887 |
| Opus 5 | $0.00022 | $0.00443 |
| Sonnet 5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00089 |
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.
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
- Use the detailed billing export, not the standard one. Resource-level attribution requires it.
- Account for credits. GCP applies multiple credit types (SUD, CUD, promotional, free tier). Always show cost before and after credits -- finance cares about both.
- SUDs are not a commitment. They auto-apply when an instance runs > 25% of the month. Don't confuse them with Committed Use Discounts.
- Per-second billing means no rounding games. Unlike AWS hourly billing, stop/start frequently is fine on GCE.
- 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_amountandcost_amountfields
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;
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.
- 6d ago First seen · 83 lines · 43 tokens per session scan A 065c39cf31a8
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.
Other cursor rules, from other repositories
galyarder-cfo-coo
Chief Financial and Operating Officer. Stability guardian. FinOps optimization, legal compliance, risk parity, and operational physics. Apex instance of the Humans 2.0 protocol.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.