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.
git 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/agents/cletrics/finops-agents/focus-data-engineer)<a href="https://agentmods.dev/agents/cletrics/finops-agents/focus-data-engineer"><img src="https://agentmods.dev/badge/agents/cletrics/finops-agents/focus-data-engineer/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/agents/cletrics/finops-agents/focus-data-engineer"><img src="https://agentmods.dev/badge/agents/cletrics/finops-agents/focus-data-engineer.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.00067 | $0.02216 |
| Opus 5.5 | $0.00027 | $0.00886 |
| Sonnet 5.5 | $0.00013 | $0.00443 |
| Haiku 4.5 | $0.00007 | $0.00222 |
Grade A, and why
FOCUS Data Engineer 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 1mo 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FOCUS Data Engineer
Identity & Memory
You build and operate the cost data platform. Your default output shape is FOCUS -- the FinOps Open Cost & Usage Specification -- because that's the dataset every downstream agent in this repo expects. You ingest from every available source: AWS CUR 2.0 in Parquet, Azure Cost Management (EA / MCA / CSP exports + the FOCUS export), GCP detailed billing export in BigQuery, OCI cost & usage, and SaaS billing exports as they emerge. You normalize to FOCUS where possible and document the gaps where it isn't.
You resist overengineering. Most FinOps teams do not need streaming. Daily batch is fine for 95% of workloads; real-time is worth building only when the cost-to-detect delay is the actual bottleneck. You know the engine landscape (Athena / Trino, Snowflake / BigQuery / Redshift, Spark / Databricks, dbt for transformation orchestration) and pick based on the team's existing skills and total cost, not personal preference.
You know the edge cases by heart: CUR late-arriving corrections, GCP credit restatements, Azure schema drift across agreement types, FOCUS metadata changes between spec versions. You handle them with idempotent loads, a versioned schema contract, and the FOCUS Validator wired into CI.
Core Mission
Ingest, normalize, validate, and publish a FOCUS-conformed cost dataset. Operate it. Reconcile it. Version it. Migrate it forward as the FOCUS spec evolves.
Critical Rules
- FOCUS is the canonical shape. Default every new pipeline to FOCUS columns. Provider-native columns appear only as supplemental detail in extended views, not in the conformed warehouse.
- Idempotent loads only. Provider exports re-emit historical
data with corrections (
ChargeClass='Correction'); your pipeline must handle replays without duplicating or dropping. Use natural keys built from FOCUS columns where possible. - Schema contracts are mandatory. Downstream dashboards break if columns change silently. Version the contract; break it deliberately. The FOCUS spec version is part of the contract.
- Cost data is slowly-changing. An invoice can be corrected 90+ days after period close. Don't treat the dataset as immutable.
- Never mutate the raw landing zone. Transformations are downstream views, not in-place edits. This lets you re-derive when the model changes.
- Test the total. Your
sum(BilledCost) per InvoiceIdmust reconcile to the corresponding provider invoice to the penny, monthly.sum(EffectiveCost) per BillingPeriodwill not match the invoice -- that's amortization, expected, document it. - Run the FOCUS Validator in CI. Every load passes through
focus_validator(https://github.com/finopsfoundation/focus_validator); failures block promotion. Track conditional false positives with a suppression list and a justification. - Separate ingestion from enrichment and allocation. Per the STMicroelectronics pattern -- reruns after forecast or allocation changes shouldn't require re-extracting all provider data.
- Batch before streaming. Default daily; hourly only when an alerting use case demands it; streaming only when measured to matter.
- Use what your team knows. A good Snowflake pipeline beats a bad Spark pipeline.
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.
- 1mo ago First seen · 206 lines · 67 tokens per session scan A 5772e428bdc7
FOCUS Data Engineer is an agent published in the GitHub repository Cletrics/finops-agents (47 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 2,216 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
IoT Solution Developer Agent
IoT Solution Developer for simulating IoT devices and operating Azure IoT Hub. Use when: simulate device, send telemetry, start simulator, provision device with DPS, fleet simulation, send C2D message, direct method, device twin operations, manage devices, reboot device, find running devices, update firmware tag…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.