A workflow guide for creating, previewing, updating, scheduling, running, and exploring Costory reports.

Use it to prepare cost reports with charts, PDFs, rankings, text, or DIGEST cost-change explanations, and to share them through Slack, Teams, or email.

It keeps report context, widgets, previews, and delivery destinations consistent across report tasks.

reports — Skill for Claude Code by costory-io

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.

Any agent

npx skills add costory-io/costory-finops-mcp-skills --skill reports

Clone the repo

git clone --depth 1 https://github.com/costory-io/costory-finops-mcp-skills

Made for: Claude Code.

Or install costory, the plugin that ships this one along with the rest of its 7 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/costory-io/costory-finops-mcp-skills/reports/github.svg)](https://agentmods.dev/skills/costory-io/costory-finops-mcp-skills/reports)

Your own site

<a href="https://agentmods.dev/skills/costory-io/costory-finops-mcp-skills/reports"><img src="https://agentmods.dev/badge/skills/costory-io/costory-finops-mcp-skills/reports/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/costory-io/costory-finops-mcp-skills/reports"><img src="https://agentmods.dev/badge/skills/costory-io/costory-finops-mcp-skills/reports.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 136 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,995 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00136	$0.06995
Opus 5	$0.00068	$0.03497
Sonnet 5	$0.00027	$0.01399
Haiku 4.5	$0.00014	$0.00700

Measured 12d ago against content hash 434f9cd89b8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

reports 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 12d 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/costory/skills/reports/SKILL.md · 454 lines

How it starts

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

Reports

Skill body version 0.5.2. Workflows here are named — Schedule, Explain, Update, Run, Explore. Older bodies lettered them A–E, and other Costory surfaces used a different letter order. If you are holding a lettered routing table for reports, it is stale: route by the names in this body and ignore the letters.

A report has a shared reportContext input (global theme) and widgets that inherit it by default. It delivers those widgets (chart snapshot, PDF, top/flop, text, or DIGEST cost-change tree) to one or more destinations (Slack, Teams, email). Same mental model as dashboards: shared context + per-widget overrides. create_report, update_report, and preview_report_widget all take the same report-level reportContext.

Temporary compatibility: the deprecated top-level context alias is accepted during migration, but always generate reportContext. Never send both.

Load this skill first for any report creation, DIGEST preview, substantial update, or delivery conversation.

Must-follow rules

Everything below this section is detail. These eight are the contract:

Ask before build (Schedule / delivery). Do not pick widgets, call preview_report_widget, or call create_report until the design is confirmed. Never silently default to a graph or an AI summary on Schedule.
Explain exception — preview-first DIGEST. For one-shot "what changed / explain last month" (Explain workflow or explain-period-change recipe), defaulting to DIGEST chat preview is required. Do not wait for a full design questionnaire; do not substitute query + compare for the first answer.
Context-first. Once answers are in, define the full reportContext before listing widgets. Widgets carry only overrides — never duplicate what already lives in reportContext.
Destinations last. Do not call list_available_destinations until the user has named the channel type (Slack / Teams / email). Then list only that type and propose matches by name — never paste a whole channel list into the conversation.
AI features are opt-in. DIGEST-only. Set display: "summary" for the executive narrative and/or enableAiInvestigation: true for per-node deep analysis — both default off (tree-only) and are slower.
Confirm delivery. Both NOW and SCHEDULED need explicit confirmation before create_report. UNSCHEDULED does not.
datePreset, never frozen dates, on SCHEDULED reports.
Cost data is ~2 days late. Prefer a Tuesday weekly send (weekday: 2) when the period is LAST_WEEK (a completed calendar week). If the report must land earlier (e.g. Monday), use TRAILING_7_DAYS instead of LAST_WEEK so the window is not a half-empty calendar week.

Read the full file on GitHub · 454 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.

12d ago First seen · 454 lines · 136 tokens per session scan A 434f9cd89b8f

Subscribe to this mod's changes

reports is a skill published in the GitHub repository costory-io/costory-finops-mcp-skills (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 136 tokens to every session and 6,995 once invoked, about $0.0007 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.

Analytics and metrics automation aws cloud-cost finops finops-mcp gcp

terraform-infrastructure-as-code

Comprehensive Terraform Infrastructure as Code skill covering resources, modules, state management, workspaces, providers, and advanced patterns for cloud-agnostic infrastructure deployment.

manutej/luxor-claude-marketplace · 36 tokens

auditing-gcp-iam-permissions

Auditing Google Cloud Platform IAM permissions to identify overly permissive bindings, primitive role usage, service account key proliferation, and cross-project access risks using gcloud CLI, Policy Analyzer, and IAM Recommender.

xalgorix/xalgorix · 51 tokens

detecting-s3-data-exfiltration-attempts

Detecting data exfiltration attempts from AWS S3 buckets by analyzing CloudTrail S3 data events, VPC Flow Logs, GuardDuty findings, Amazon Macie alerts, and S3 access patterns to identify unauthorized bulk downloads and cross-account data transfers.

xalgorix/xalgorix · 63 tokens

implementing-cloud-trail-log-analysis

Implementing AWS CloudTrail log analysis for security monitoring, threat detection, and forensic investigation using Athena, CloudWatch Logs Insights, and SIEM integration to identify unauthorized access, privilege escalation, and suspicious API activity.

xalgorix/xalgorix · 50 tokens

performing-aws-privilege-escalation-assessment

Performing authorized privilege escalation assessments in AWS environments to identify IAM misconfigurations that allow users or roles to elevate their permissions using Pacu, CloudFox, Principal Mapper, and manual IAM policy analysis techniques.

xalgorix/xalgorix · 54 tokens

performing-cloud-log-forensics-with-athena

Uses AWS Athena to query CloudTrail, VPC Flow Logs, S3 access logs, and ALB logs for forensic investigation. Covers CREATE TABLE DDL with partition projection, forensic SQL queries for detecting unauthorized access, data exfiltration, lateral movement, and privilege escalation. Use when investigating AWS security…

xalgorix/xalgorix · 80 tokens