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 costory-io/costory-finops-mcp-skills --skill querygit clone --depth 1 https://github.com/costory-io/costory-finops-mcp-skillsWrote 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/costory-io/costory-finops-mcp-skills/query)<a href="https://agentmods.dev/skills/costory-io/costory-finops-mcp-skills/query"><img src="https://agentmods.dev/badge/skills/costory-io/costory-finops-mcp-skills/query/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/costory-io/costory-finops-mcp-skills/query"><img src="https://agentmods.dev/badge/skills/costory-io/costory-finops-mcp-skills/query.svg" alt="Reviewed on agentmods" width="80" 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.00093 | $0.06292 |
| Opus 5.5 | $0.00037 | $0.02517 |
| Sonnet 5.5 | $0.00019 | $0.01258 |
| Haiku 4.5 | $0.00009 | $0.00629 |
Grade A, and why
query 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 18d 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 — 556 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query
query is the unified Costory explorer for cost, usage, saved metrics, external metrics, formulas, and budgets. Supporting tools discover dimensions, pick a groupBy, resolve metric IDs, and suggest next steps — call them before guessing field names.
Load this skill first for investigation, breakdowns, comparisons, unit economics (cost per X), or budget burn analysis.
When to Trigger
- Exploring or breaking down cloud costs (by service, region, team, environment, …)
- Explorer-style period comparison (PoP totals / composition) — not the “why did spend move?” change-tree explanation
- Cost + usage or cost + business metric (unit economics / formulas)
- Budget vs spend, including month-to-date rolling burn and cumulated budget vs cumulated cost
- K8s waste vs K8s cost (usage metrics + optional waste ratio)
- Effective savings (
contracted_costminuseffective_cost) - Validating CEL filters before building a dashboard or report
- User asks "what are we spending on X?"
- After a DIGEST explain preview: drill into a user-named node with
filterCel
Hand off instead of this skill: "why did the bill jump?" / "what changed last month?" / "explain the spike" → load recipes → explain-period-change (or reports Explain). First answer is preview_report_widget DIGEST, not query + compare.
Core concepts
SCOPE vs SPLIT
| Idea | Field | Meaning | Example |
|---|---|---|---|
| SPLIT | groupBy |
How to break the result into series/rows | "Cost per environment" → groupBy: "cos_environment", no filter |
| SCOPE | filterCel |
Which rows to include (CEL) | "EC2 costs" → filterCel: "cos_service_name in [\"AmazonEC2\"]", groupBy something else |
| Combined | both | Scoped breakdown | "EC2 per region" → filter EC2 + groupBy: "cos_region" |
Never put the split dimension into filterCel (or the filter into groupBy). Discover exact CEL names with search (type: ["dimensions"]) — Costory labels use a cos_ prefix (e.g. cos_service_name).
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.
- 18d ago Changed b98769114abd
- 1mo ago Changed · +1 lines ecaa19dede8f
- 1mo ago Changed · +3 lines 67027d00783f
- 1mo ago First seen · 552 lines · 93 tokens per session scan A dc0828c3fedd
query is a skill published in the GitHub repository costory-io/costory-finops-mcp-skills (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 93 tokens to every session and 6,292 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
finops-expert
Expert-level cloud financial operations, cost optimization, and cloud economics. Use when the user mentions cloud cost, optimization, cloud economics, or AWS cost, or when the task involves FinOps Fundamentals, Cost Management, FinOps Practices, or Cost Visibility.
cost-check
Estimate the monthly cost of a Pulumi or Terraform project with the FinFocus CLI, flag expensive resources, cost increases, and total cost against thresholds in .cost-check.yml, and write a COSTCHECK.md report. Reads machine-readable JSON, checks the CLI version, and names what to do when the CLI, a plugin…
cost-drift
Compare actual and projected spend for a Pulumi stack with the FinFocus CLI, flag drifting resources against thresholds in .cost-check.yml, explain likely causes, track the trend, and write a COSTDRIFT.md report. Reads machine-readable JSON, checks the CLI version, and names what to do when the CLI, a billing plugin…
finfocus-budget
Configure, check, and troubleshoot FinFocus budget thresholds. Use when setting cost.budgets in config.hujson, reading budget health, filtering scopes with --budget-scope, or making cost projected, cost actual, or overview exit non-zero in CI. Triggers on: "finfocus budget", "budget threshold", "exit-on-threshold"…
finfocus-plugin-dev
Implement and maintain a FinFocus cost plugin in a repository scaffolded by finfocus plugin init. Use when adding or changing pricing logic in a plugin, adding a resource type, writing the Supports handler, returning GetProjectedCost or GetActualCost results, testing a plugin locally against a Pulumi plan, or…
gcp-dispute-kit
Use to assemble a dispute-grade evidence packet and ready-to-file letters after GCP API-key fraud (leaked-key abuse, runaway Gemini/Vertex charges). READ-ONLY — mutates nothing. Triggers on "dispute gcp charges", "google cloud fraud refund", "gemini api fraud dispute", "gcp billing dispute", "chargeback google cloud".