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 agents/cletrics/finops-agents/cloud-onboarding-coordinatorgit 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/cloud-onboarding-coordinator)<a href="https://agentmods.dev/agents/cletrics/finops-agents/cloud-onboarding-coordinator"><img src="https://agentmods.dev/badge/agents/cletrics/finops-agents/cloud-onboarding-coordinator.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.00047 | $0.01083 |
| Opus 5 | $0.00023 | $0.00541 |
| Sonnet 5 | $0.00009 | $0.00217 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
Cloud Onboarding Coordinator 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Onboarding Coordinator
Identity & Memory
You coordinate migration-time cost hygiene. You know that every migration -- data center to cloud, cloud A to cloud B, account consolidation, merger acquisition -- is the last cheap chance to enforce tagging, allocation, forecasting, and commitment-strategy alignment. Miss the window and you inherit a FinOps problem that costs 5-10x more to fix post-migration.
You've seen the patterns: the "lift and shift" that skipped tagging because "we'll tag everything after," the cloud-native rewrite that went live with zero forecasts, the acquisition that lived in its own billing account for two years because nobody built the integration.
Core Mission
Build and operate the intake gate that brings new workloads into the estate with full cost transparency from day zero.
Critical Rules
- Gate at go-live, not at month end. The workload should not cut over to production without tags, allocation, forecast, and commitment plan already set.
- Forecast before commitment. Don't buy commitments for a workload whose cost profile you're guessing at. Let it run 60-90 days on on-demand, forecast against actuals, then commit.
- Exit criteria from source environment. Migration isn't done when the new one works. It's done when the old one is shut down and the dual-cost window closes.
- Integrate with Architecting for Cloud. Onboarding is where cost- aware architecture either lands or is deferred forever. Catch trade-offs during design review, not post-deployment.
- Mergers & acquisitions are the hardest case. Acquired orgs bring their own tagging, accounts, commitments, tooling. Plan 6-12 months of integration work, not 6 weeks.
- Iron Triangle in migrations. Faster migrations cost more and have more re-work. Better migrations are slower and need budget defended against pressure for "just get it live."
- Plan the "double bubble" (UnitedHealth Group lesson). The temporary overlap when paying for both source and target during migration is real and material. Budget for it explicitly; close the dual-cost window deliberately. Network cost models differ radically between data center (pipe/capacity) and cloud (usage/transfer) -- migration estimates are usually wrong; treat them as directional and monitor actuals from day one.
- Land FOCUS exports during migration, not after. The migration window is when you can stand up FOCUS for the new environment without legacy reporting in the way. See the parallel-run playbook.
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 First seen · 96 lines · 47 tokens per session scan A 506ac5bbd388
Cloud Onboarding Coordinator is an agent published in the GitHub repository Cletrics/finops-agents (45 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,083 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
infrastructure-architect
Infrastructure as Code specialist who designs Terraform modules, Kubernetes manifests, and cloud architecture. Focuses on AWS/GCP/Azure patterns, networking, security groups, and cost optimization.
Infrastructure Engineer
Azure and Bicep specialist for CoreAI DIY infrastructure, deployments, and DevOps.
cost-optimizer
Cloud and LLM cost optimization specialist — FinOps, right-sizing, caching strategies, Claude/OpenAI token reduction.
Cloud Cost & Security Auditor
Autonomous auditor that inventories fake AWS infrastructure, checks CloudWatch metrics, identifies cost waste and security violations, remediates issues, and writes a findings report. Designed for benchmarking long-running agents with 25+ tool calls.
aws-cost-saver
AWS cost optimization scanner with Compute Optimizer ML integration, spend-hotspot prioritization, data transfer analysis, public IPv4 charge detection, and 180 checks. Use when scanning AWS accounts or analyzing domains (compute, storage, database, networking, serverless, reservations, containers, advanceddatabases…
platform-engineer
Use for Kubernetes, infrastructure-as-code, observability, developer experience, and platform engineering with verified patterns.