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.06226 |
| Opus 5 | $0.00046 | $0.03113 |
| Sonnet 5 | $0.00019 | $0.01245 |
| Haiku 4.5 | $0.00009 | $0.00623 |
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 yesterday.
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.
- yesterday Changed · +1 lines ecaa19dede8f
- 7d ago Changed · +3 lines 67027d00783f
- 11d 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 2d ago), licensed Apache-2.0. It adds 93 tokens to every session and 6,226 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-08-31.
Other skills, from other repositories
querying-well-data
How to query a Well workspace correctly — discover the schema first, then query the right root. Use whenever the user asks about their invoices, companies, contacts, bank transactions, accounts, or accounting ledger in Well, or before writing any wellqueryrecords call.
ar-aging
Produce an accounts-receivable aging report and surface overdue invoices for a Well workspace. Use when the user asks who owes them money, an AR aging report, overdue invoices, days sales outstanding (DSO), or which customers to chase.
balance-sheet
Build a balance sheet (bilan) from a Well workspace. Use when the user asks for a balance sheet, bilan, assets/liabilities/equity, or financial position at a point in time.
cash-flow-forecast
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions. Use when the user asks for a cash-flow forecast, runway, how long until they run out of cash, projected balance, or expected inflows/outflows.
compte-de-resultat
Build a profit & loss statement (compte de résultat / income statement) from a Well workspace. Use when the user asks for a P&L, income statement, compte de résultat, revenue vs expenses, or net result over a period.
month-end-close
Run a month-end (or period) close checklist against a Well workspace — verify everything is reconciled and posted before the books are closed. Use when the user asks to close the month/period, run a close checklist, check if the books are ready to close, or what's left before closing.