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 khalilbenaz/claude-skills-collection --skill cloud-migration-plannergit clone --depth 1 https://github.com/khalilbenaz/claude-skills-collectionWrote 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/khalilbenaz/claude-skills-collection/cloud-migration-planner)<a href="https://agentmods.dev/skills/khalilbenaz/claude-skills-collection/cloud-migration-planner"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/cloud-migration-planner/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/khalilbenaz/claude-skills-collection/cloud-migration-planner"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/cloud-migration-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.01770 |
| Opus 5 | $0.00041 | $0.00885 |
| Sonnet 5 | $0.00016 | $0.00354 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
cloud-migration-planner 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Migration Planner
Workflow en 8 étapes
1. Inventaire applicatif
Cartographier chaque application : stack technique, dépendances inter-services, flux réseau, volumes de données, SLAs.
Outils recommandés :
- AWS : AWS Application Discovery Service (
aws discovery start-import-task) - Azure : Azure Migrate (
az migrate project create) - GCP : Migrate to Virtual Machines + Service Catalog
Livrable minimal : tableur avec colonnes App | Stack | Deps | Trafic (Go/mois) | RTO | RPO | Owner.
2. Assessment de compatibilité
Pour chaque application, évaluer sur 4 axes (noter de 1 à 5) :
| Axe | Questions clés |
|---|---|
| Complexité technique | Couplage fort ? API propriétaire ? OS obsolète ? |
| Criticité métier | Impact si down > 1h ? Régulé ? |
| Dépendances | Combien de services liés ? Dépendances cycliques ? |
| Portabilité | Stateless ? Containerisable ? Licences cloud-compatible ? |
Score ≤ 8/20 → candidat Retire/Retain. Score ≥ 15/20 → candidat Refactor.
3. Stratégie par application (6 R's)
| Stratégie | Quand choisir | Effort | Gain cloud |
|---|---|---|---|
| Rehost (lift-and-shift) | VM legacy, contrainte temps | Faible | Faible |
| Replatform | DB vers RDS/Managed, peu de code | Moyen | Moyen |
| Refactor | App stratégique, cloud-native cible | Élevé | Fort |
| Repurchase | Remplacer par SaaS (ex. CRM → Salesforce) | Moyen | Variable |
| Retire | App inutilisée ou redondante | Minimal | — |
| Retain | App réglementée ou trop risquée pour migrer | — | — |
Règle empirique 2026 : 40-50 % Rehost pour la 1ère vague, puis réduire à mesure que les équipes montent en compétence.
4. Architecture cloud cible
Concevoir avant de migrer. Points incontournables :
Réseau :
On-premise ──[ VPN IPSec / ExpressRoute / Direct Connect ]──► VPC/VNet
├── Subnet public (Load Balancer, Bastion)
├── Subnet privé (App Tier)
└── Subnet data (DB, Cache)
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 · 172 lines · 81 tokens per session scan A e24758be4ddf
cloud-migration-planner is a skill published in the GitHub repository khalilbenaz/claude-skills-collection (22 stars, last pushed 19d ago), licensed MIT. It adds 81 tokens to every session and 1,770 once invoked, about $0.0004 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 skills, from other repositories
docker-devops
Docker/K8s: Dockerfile, multi-stage, compose, manifests, Helm. Triggers: Docker, Dockerfile, container, Kubernetes, k8s, compose, Helm, pod.
rollback
Rolls back git commit, DB migration, or deploy to known-good with safety + health checks. Triggers: rollback, revert deploy, revert migration, rollback commit, git revert.
health
Service/infra health via liveness/readiness checks, resource usage, quick diagnostics. Triggers: health check, services up, system status, infra health, degraded service.
monitoring-alerting
Monitoring and alerting design reviewer for production backend services. ALWAYS use when writing Prometheus alerting rules, designing Grafana dashboards, defining SLI/SLO, configuring alert routing (PagerDuty/OpsGenie/Slack), or reviewing existing monitoring setups. Covers SLI/SLO definition, alert rule quality…
piggyback-hosting
Hosting-Muster, um eine lokal gebaute Anwendung (eigene Datenbank, eigener API-Key, In-Process-State) sicher hostbar zu machen, ohne Nutzerverwaltung zu bauen. Kernzug — der Host speichert nichts, der Browser des Besuchers speichert alles — sodass Pro-Besucher-Accounts, Zugriffsprüfungen und Löschfristen…
cloud-communication-protocols
Dach-Skill für Cloud-gestützte Kommunikationsprotokolle zwischen Agenten auf unterschiedlichen Maschinen (Ping-Pong, agent-beam, Listener und künftige Protokolle). Nutzen, wenn Arbeit über Maschinen hinweg per gemeinsamem Sync-Ordner oder Message-Yard koordiniert wird.