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/arjunprabhulal/devops-skills/cloud-migrationnpx skills add arjunprabhulal/devops-skills --skill cloud-migrationgit clone --depth 1 https://github.com/arjunprabhulal/devops-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/arjunprabhulal/devops-skills/cloud-migration)<a href="https://agentmods.dev/skills/arjunprabhulal/devops-skills/cloud-migration"><img src="https://agentmods.dev/badge/skills/arjunprabhulal/devops-skills/cloud-migration.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.00120 | $0.01186 |
| Opus 5 | $0.00060 | $0.00593 |
| Sonnet 5 | $0.00024 | $0.00237 |
| Haiku 4.5 | $0.00012 | $0.00119 |
Grade A, and why
cloud-migration 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 3d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Migration
A migration that copies the current architecture verbatim into a new provider ships the current architecture's problems to a new address, plus a new set of provider-specific quirks nobody has learned yet. The move itself is rarely the hard part; deciding what to actually change during the move is.
Every workload deserves an explicit choice among the 6 Rs before it gets touched, and every cutover deserves a rollback plan tested before the migration is called done. Decide what you're changing on purpose, and prove you can go back before you can't.
1. Assign each workload one of the 6 Rs, deliberately
The 6 Rs — retire, retain, rehost, replatform, repurchase, refactor — are a forcing function against defaulting everything to "rehost" (lift-and-shift) because it's the least work upfront. Rehosting is often correct for low-value or soon-to-be-decommissioned systems; it's usually wrong for anything that will live for years, because it carries forward architectural debt at cloud prices instead of on-prem prices.
- Retire what nobody uses — the cheapest migration is not migrating.
- Rehost for speed when the system is stable and not worth re-architecting yet.
- Replatform to pick up a managed equivalent (self-run DB to managed DB) without a full rewrite.
- Refactor only when the business value of the change justifies the schedule risk.
Done when: every workload in scope has an assigned R and a one-line reason for it.
2. Sequence the migration by dependency and risk, not by ease
Migrate low-risk, low-dependency workloads first to build confidence in the process and tooling, but track the full dependency graph so you don't strand a migrated service that still needs to call something on the old side. Cross-environment calls during migration usually mean higher latency and a temporary hybrid network — plan that connectivity explicitly rather than discovering it's needed mid-cutover.
Done when: the migration order respects the dependency graph and no step assumes a dependency has already moved when it hasn't.
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.
- 3d ago First seen · 98 lines · 120 tokens per session scan A 3dbe54e4aa65
cloud-migration is a skill published in the GitHub repository arjunprabhulal/devops-skills (2 stars, last pushed 9d ago), licensed MIT. It adds 120 tokens to every session and 1,186 once invoked, about $0.0006 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
google-mobile-ads-android-migrate-to-next-gen
Migrates Android applications from the old, legacy Google Mobile Ads (GMA) SDK (com.google.android.gms:play-services-ads) to the new GMA Next-Gen SDK (com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk). Provides comprehensive mapping tables for imports, classes, and method signatures to help determine…
agent-platform-deploy
Deploy open models or custom weights from Model Garden to Agent Platform endpoints, check the status of an in-progress deployment operation, or clean up resources by undeploying models and deleting endpoints. Use when asked to actively deploy a model, list the Model Garden CATALOG of available models, check if a…
agent-platform-eval-flywheel
Measures and improves the quality of AI models and agents on Google Cloud using the Eval Quality Flywheel methodology. Use when evaluating an agent or model, building an eval dataset, picking or writing evaluation metrics, analyzing failures, comparing results before and after a fix, or when guidance is needed on…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).
gcloud
Provides safety-critical validation, guardrails, and data reduction for gcloud CLI operations across Google Cloud Platform (GCP) services and infrastructure. Use when planning, generating, constructing, proposing, describing, or executing any gcloud CLI commands - including when answering questions about gcloud…
cloud-monitoring-list-time-series-request
Generates valid Cloud Monitoring ListTimeSeries requests and aggregation specifications from metric descriptors and resource parameters. Use when asked to create, generate, format, or build ListTimeSeries requests, JSON payloads, filter expressions, or aligner/reducer aggregations for Cloud Monitoring metrics and…