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 skills add cline/skills --skill gcp-to-awsgit clone --depth 1 https://github.com/cline/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/cline/skills/gcp-to-aws)<a href="https://agentmods.dev/skills/cline/skills/gcp-to-aws"><img src="https://agentmods.dev/badge/skills/cline/skills/gcp-to-aws/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/skills/cline/skills/gcp-to-aws"><img src="https://agentmods.dev/badge/skills/cline/skills/gcp-to-aws.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.00311 | $0.06376 |
| Opus 5 | $0.00156 | $0.03188 |
| Sonnet 5 | $0.00062 | $0.01275 |
| Haiku 4.5 | $0.00031 | $0.00638 |
Grade A, and why
gcp-to-aws 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 11d 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GCP-to-AWS Migration Skill
Philosophy
- Re-platform by default: Select AWS services that match GCP workload types (e.g., Cloud Run → Fargate, Cloud SQL → RDS).
- Dev sizing unless specified: Default to development-tier capacity (e.g., db.t4g.micro, single AZ). Upgrade only on user direction.
- No human one-time migration costs: Do not present human labor, professional services, or people-time work as dollar estimates or "one-time migration cost" budget categories. Vendor charges grounded in data (for example GCP data transfer egress in the infra estimate when billing exists) are allowed.
- Multi-signal approach: Design phase adapts based on available inputs — Terraform IaC for infrastructure, billing data for service mapping, and app code for AI workload detection.
- BigQuery /
google_bigquery_*: The skill does not recommend a specific AWS analytics or warehouse service. During Clarify, if discovery shows BigQuery (IaCgoogle_bigquery_*and/or billing rows for BigQuery), you must surface the specialist advisory before Design (seereferences/phases/clarify/clarify.md). Design output usesDeferred — specialist engagement; keep directing the user to their AWS account team and/or a data analytics migration partner through Design, Estimate, and docs (seereferences/phases/design/design-infra.mdBigQuery specialist gate).
Definitions
- "Load" = Read the file using the Read tool and follow its instructions. Do not summarize or skip sections.
$MIGRATION_DIR= The run-specific directory under.migration/(e.g.,.migration/0226-1430/). Set during Phase 1 (Discover).
Context Loading Rules
Each phase loads reference files on demand. To keep per-turn context manageable and prevent instruction-following degradation:
- Budget: Each phase should load no more than ~800 lines of instructions (excluding user artifacts like JSON profiles and MCP tool results).
- Conditional loading: Reference files with trigger conditions (e.g.,
agentic_profile.is_agentic == true) MUST NOT be loaded unless the condition is met. Do not speculatively load files. - No duplication: Model mapping tables, pricing data, and shared warnings exist in one canonical file. Other files reference them; they do not copy them inline.
- Progressive depth: Phase orchestrators (
design.md,generate.md) contain short routing logic that points to detailed sub-files. Load the sub-file only when its path is selected.
What ships with it
60 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.
- data/sdk-capability-map.json 1.1 KB
- references/clustering/terraform/classification-rules.md 6.5 KB
- references/clustering/terraform/clustering-algorithm.md 7.9 KB
- references/clustering/terraform/depth-calculation.md 4.5 KB
- references/clustering/terraform/typed-edges-strategy.md 4.6 KB
- references/design-refs/ai-anthropic-to-bedrock.md 2.9 KB
- references/design-refs/ai-gemini-to-bedrock.md 15 KB
- references/design-refs/ai-openai-to-bedrock.md 17 KB
- references/design-refs/ai.md 3.4 KB
- references/design-refs/compute.md 6.8 KB
- references/design-refs/database.md 9.1 KB
- references/design-refs/design-ref-agentic-to-agentcore.md 19 KB
- references/design-refs/design-ref-harness.md 7.9 KB
- references/design-refs/fast-path.md 10 KB
- references/design-refs/index.md 6.2 KB
- references/design-refs/messaging.md 3.5 KB
- references/design-refs/networking.md 5.5 KB
- references/design-refs/security.md 3.8 KB
- references/design-refs/storage.md 4.7 KB
- references/phases/clarify/clarify-ai-only.md 16 KB
- references/phases/clarify/clarify-ai.md 58 KB
- references/phases/clarify/clarify-compute.md 10.0 KB
- references/phases/clarify/clarify-database.md 11 KB
- references/phases/clarify/clarify-global.md 24 KB
- references/phases/clarify/clarify.md 50 KB
- references/phases/design/design-ai.md 30 KB
- references/phases/design/design-billing.md 13 KB
- references/phases/design/design-infra.md 13 KB
- references/phases/design/design.md 4.5 KB
- references/phases/discover/discover-app-code.md 42 KB
- references/phases/discover/discover-billing.md 7.2 KB
- references/phases/discover/discover-iac.md 33 KB
- references/phases/discover/discover-preview.md 20 KB
- references/phases/discover/discover.md 12 KB
- references/phases/estimate/estimate-ai.md 17 KB
- references/phases/estimate/estimate-billing.md 12 KB
- references/phases/estimate/estimate-infra.md 47 KB
- references/phases/estimate/estimate.md 8.1 KB
- references/phases/feedback/feedback-trace.md 4.5 KB
- references/phases/feedback/feedback.md 3.2 KB
- references/phases/generate/generate-ai.md 14 KB
- references/phases/generate/generate-artifacts-ai.md 34 KB
- references/phases/generate/generate-artifacts-billing.md 6.1 KB
- references/phases/generate/generate-artifacts-docs.md 21 KB
- references/phases/generate/generate-artifacts-infra.md 43 KB
- references/phases/generate/generate-artifacts-report.md 40 KB
- references/phases/generate/generate-artifacts-scripts.md 15 KB
- references/phases/generate/generate-billing.md 16 KB
- references/phases/generate/generate-infra.md 22 KB
- references/phases/generate/generate.md 7.9 KB
- references/shared/ai-migration-guardrails.md 6.6 KB
- references/shared/ai-model-lifecycle.md 8.8 KB
- references/shared/bedrock-quotas.md 7.1 KB
- references/shared/handoff-gates.md 4.7 KB
- references/shared/migration-complexity.md 11 KB
- references/shared/pricing-cache.md 41 KB
- references/shared/pricing-fallback.md 1.5 KB
- references/shared/retarget-gotchas.md 11 KB
- references/shared/schema-discover-ai.md 17 KB
- references/shared/schema-discover-billing.md 5.0 KB
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.
- 11d ago First seen · 365 lines · 311 tokens per session scan A 4cde0ad97d0c
gcp-to-aws is a skill published in the GitHub repository cline/skills (23 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 311 tokens to every session and 6,376 once invoked, about $0.0016 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-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…