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 skills/rshade/finfocus/finfocus-costnpx skills add rshade/finfocus --skill finfocus-costgit clone --depth 1 https://github.com/rshade/finfocusWrote 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/rshade/finfocus/finfocus-cost)<a href="https://agentmods.dev/skills/rshade/finfocus/finfocus-cost"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/finfocus-cost.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 | $0.00102 | $0.01018 |
| Opus 5 | $0.00051 | $0.00509 |
| Sonnet 5 | $0.00020 | $0.00204 |
| Haiku 4.5 | $0.00010 | $0.00102 |
Grade A, and why
finfocus-cost 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 5d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinFocus Cost Analysis
Projected Costs
Estimate future costs from a Pulumi preview:
# From Pulumi JSON
finfocus cost projected --pulumi-json plan.json
# With output format
finfocus cost projected --pulumi-json plan.json --output json
# With specific adapter
finfocus cost projected --pulumi-json plan.json --adapter aws-public
# Auto-detect Pulumi project (searches for Pulumi.yaml)
finfocus cost projected
Generate Pulumi JSON: pulumi preview --json > plan.json
Actual Costs
Fetch historical costs from cloud providers:
# Basic usage
finfocus cost actual --pulumi-json plan.json --from 2024-01-01
# Date range
finfocus cost actual --pulumi-json plan.json --from 2024-01-01 --to 2024-01-31
# With grouping
finfocus cost actual --pulumi-json plan.json --from 2024-01-01 --group-by daily
finfocus cost actual --pulumi-json plan.json --from 2024-01-01 --group-by monthly
# Cross-provider aggregation
finfocus cost actual --group-by daily --from 2024-01-01 --to 2024-01-31
Date formats: 2006-01-02 or RFC3339. --to defaults to now.
Recommendations
Get cost optimization suggestions:
# All recommendations
finfocus cost recommendations --pulumi-json plan.json
# Filter by action type
finfocus cost recommendations --pulumi-json plan.json --action-type RIGHTSIZE,TERMINATE
# Dismiss/undismiss
finfocus cost recommendations dismiss <id>
finfocus cost recommendations undismiss <id>
finfocus cost recommendations history
Valid action types: RIGHTSIZE, TERMINATE, PURCHASE_COMMITMENT, ADJUST_REQUESTS, MODIFY, DELETE_UNUSED, MIGRATE, CONSOLIDATE, SCHEDULE, REFACTOR, INVESTIGATE, OTHER.
Budgets
Monitor cloud spending against budget limits:
# View budgets
finfocus cost budget
# Filter by provider
finfocus cost budget --filter "provider=kubecost"
# Filter by tags
finfocus cost budget --filter "tag:namespace=production"
finfocus cost budget --filter "tag:namespace=prod-*" # Glob patterns
# Combined filters
finfocus cost budget --filter "provider=aws" --filter "tag:env=staging"
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 151 lines · 102 tokens per session scan A 11f3a90fcc41
finfocus-cost is a skill published in the GitHub repository rshade/finfocus (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 102 tokens to every session and 1,018 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
dashboards
Use when creating or extending Costory dashboards, generating interesting FinOps overviews (suggestgroupby + suggestusagemetrics + text widgets), adding or replacing widgets, copying widgets between dashboards, editing dashboardContext (global filter / period / groupBy) via updatedashboard, or applying shared-context…
query
Use when exploring Costory cost, usage, metric, formula, budget, or external-metric data with the query tool — scope vs split (filterCel / groupBy), explorer PoP comparison, CEL discovery, unit economics, budgets. Not for one-shot "what changed last month" change trees — those use recipes explain-period-change /…
cost-change-investigation
Use when investigating a cost change to explain what changed, when, and the best-supported drivers with contribution, timing, usage, metric, event, alert, and terminology evidence. Call getskill with skillId "cost-change-investigation" before starting the investigation.
recipes
Use when a user states a FinOps outcome rather than a tool. Route to one recipe card, then hand off: bill jump → explain-period-change (DIGEST preview); marketplace → marketplace-spend; K8s namespace → namespace-cost; credits runway → provider-credits; GCP spend CUD leftover → gcp-spend-cud; YTD credits →…
cost-optimization
Cloud Cost Optimization & FinOps: Helps analyze and reduce cloud infrastructure costs, optimize resource usage, implement FinOps practices, and find savings opportunities. Use whenever the user mentions 'cloud costs', 'AWS bill', 'cost optimization', 'FinOps', 'right-sizing', 'reserved instances', 'savings plans'…
meter-chargeback
CocoMeter chargeback and FinOps governance. Usage: $meter chargeback refresh | $meter chargeback invoice | $meter chargeback onboarding.