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 application-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/application-migration)<a href="https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/application-migration"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/application-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/application-migration"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/application-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.00110 | $0.01361 |
| Opus 5 | $0.00055 | $0.00681 |
| Sonnet 5 | $0.00022 | $0.00272 |
| Haiku 4.5 | $0.00011 | $0.00136 |
Grade A, and why
application-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 9d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application Migration
Plan and execute application migration projects—from legacy system modernization to cloud migration and technology stack transformation.
Migration Workflow
Follow this systematic approach for successful migrations:
1. Assess Current State
Analyze the application portfolio and environment:
Actions:
- Create application inventory (name, tech stack, dependencies)
- Map data flows and integration points
- Identify business criticality (critical/important/low)
- Document compliance requirements (PCI-DSS, HIPAA, GDPR, etc.)
- Measure current performance metrics (response time, throughput, uptime)
Output: Application assessment report with complexity scores (low/medium/high)
Example Assessment:
Application: Customer Portal
Tech Stack: Java 8, Oracle 11g, Apache Tomcat 7
Dependencies: Payment Gateway API, CRM System, Email Service
Business Criticality: Critical (revenue-generating)
Complexity: High (20+ integrations, legacy code)
→ Recommendation: Strangler fig pattern with 12-month timeline
2. Select Migration Strategy
Choose the approach based on complexity and business constraints:
Strangler Fig Pattern (recommended for complex applications):
- Build new functionality alongside old system
- Incrementally redirect traffic to new components
- Retire old components gradually
- Timeline: 6-18 months
- Risk: Low (gradual transition with rollback capability)
Big Bang Migration (for simple applications):
- Complete migration in single cutover event
- All users switch simultaneously
- Timeline: 1-3 months
- Risk: High (no gradual rollback option)
Phased Migration (for multi-tenant or regional deployments):
- Migrate one tenant/region at a time
- Validate each phase before proceeding
- Timeline: 3-12 months
- Risk: Medium (parallel operations required)
3. Plan Migration
Create detailed execution roadmap with these components:
Timeline: Define phases with 2-week sprint cycles Resources: Allocate developers (3-10), QA (2-4), DevOps (1-2), architects (1) Budget: Estimate 1.5-2x initial projection (migrations typically exceed estimates) Risk Mitigation: Document top 5 risks with contingency plans Rollback Plan: Test rollback procedures before cutover
What ships with it
7 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.
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.
- 9d ago First seen · 151 lines · 110 tokens per session scan A 80a3278f8cc1
application-migration is a skill published in the GitHub repository DauQuangThanh/hanoi-rainbow (16 stars, last pushed 7mo ago), licensed MIT. It adds 110 tokens to every session and 1,361 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.