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 DauQuangThanh/hanoi-rainbow --skill platform-migrationgit clone --depth 1 https://github.com/DauQuangThanh/hanoi-rainbowWrote 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/dauquangthanh/hanoi-rainbow/platform-migration)<a href="https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/platform-migration"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/platform-migration/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/dauquangthanh/hanoi-rainbow/platform-migration"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/platform-migration.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.00114 | $0.01544 |
| Opus 5 | $0.00057 | $0.00772 |
| Sonnet 5 | $0.00023 | $0.00309 |
| Haiku 4.5 | $0.00011 | $0.00154 |
Grade A, and why
platform-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 10d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Migration
Overview
This skill provides comprehensive guidance for migrating infrastructure platforms, cloud providers, container orchestration systems, CI/CD pipelines, and observability stacks. Focus is on infrastructure-level migrations that complement application modernization efforts.
Platform migrations are infrastructure-focused and should be paired with application migration strategies. Use cloud-neutral design patterns to reduce future migration effort, though multi-cloud strategies increase complexity while reducing vendor lock-in.
Core Migration Principles
Key Practices:
- Test everything in non-production first
- Automate using Infrastructure as Code (IaC)
- Migrate incrementally rather than "big bang"
- Maintain both platforms during stabilization
- Budget 20-30% more time than estimated
- Document architecture decisions and rationale
Avoid These Pitfalls:
- Migrating everything at once without phased approach
- Skipping non-production validation
- Ignoring cost estimation for target platform
- Failing to optimize during migration (pure lift-and-shift)
- Inadequate monitoring during transition
- Leaving resources running on both platforms post-migration
Migration Workflow
Step 1: Assessment and Planning
Identify Migration Type:
- Cloud-to-cloud (AWS↔GCP↔Azure)
- Kubernetes cluster migration (EKS→GKE→AKS)
- CI/CD platform change (Jenkins→GitLab→GitHub Actions)
- Monitoring stack migration (Prometheus→Datadog→New Relic)
- Container registry migration (Docker Hub→ECR→GCR→ACR)
- Network infrastructure transformation
- Infrastructure as Code migration (Terraform→CloudFormation→Bicep)
For detailed migration type workflows: See migration-types.md
Step 2: Inventory and Dependencies
- Document all resources in source platform
- Map dependencies between components
- Identify proprietary services without direct equivalents
- Estimate costs in target platform
- Assess technical constraints and requirements
What ships with it
10 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.
- references/container-registry-migration.md 723 B
- references/cost-optimization-during-migration.md 816 B
- references/database-platform-migration.md 928 B
- references/infrastructure-as-code-migration.md 1007 B
- references/migration-principles.md 1.6 KB
- references/migration-tools.md 787 B
- references/migration-types.md 9.5 KB
- references/network-infrastructure-migration.md 731 B
- references/post-migration-validation.md 792 B
- references/risk-management.md 833 B
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.
- 10d ago First seen · 190 lines · 114 tokens per session scan A b5fe1f857b8d
platform-migration is a skill published in the GitHub repository DauQuangThanh/hanoi-rainbow (16 stars, last pushed 7mo ago), licensed MIT. It adds 114 tokens to every session and 1,544 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
spec-driven-development
Spec-first workflow where an executable, testable specification is written before code and becomes the single source of truth that tests verify against, flowing spec → acceptance criteria → tasks → implementation.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
tcapi
A helper for managing Tencent Cloud resources through Tencent Cloud's command-line API tool. Tencent Cloud is a cloud-services provider offering products such as virtual servers, storage, networks, and containers.