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 multi-cloud-strategistgit 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/multi-cloud-strategist)<a href="https://agentmods.dev/skills/khalilbenaz/claude-skills-collection/multi-cloud-strategist"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/multi-cloud-strategist/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/multi-cloud-strategist"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/multi-cloud-strategist.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.00071 | $0.02010 |
| Opus 5 | $0.00036 | $0.01005 |
| Sonnet 5 | $0.00014 | $0.00402 |
| Haiku 4.5 | $0.00007 | $0.00201 |
Grade A, and why
multi-cloud-strategist 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Cloud Strategist
Workflow
1. Qualifier la motivation réelle
Avant toute décision architecturale, identifier POURQUOI le multi-cloud est envisagé :
| Motivation | Approche recommandée |
|---|---|
| Résilience géographique | Active-active ou active-passive sur 2 clouds |
| Best-of-breed services | Couplage ciblé + abstraction aux interfaces |
| Contrainte réglementaire (souveraineté) | Cloud souverain ou zone dédiée + federation |
| Levier tarifaire / négociation | Single-cloud suffisant ; éviter la complexité inutile |
| Évitement du lock-in | Évaluer le surcoût opérationnel réel avant de continuer |
Règle d'or : si la seule raison est "au cas où", le surcoût multi-cloud n'est pas justifié.
2. Inventaire et scoring des workloads
Pour chaque service, noter sur 3 axes (0–3) :
- Couplage cloud-natif : utilise-t-il des services propriétaires (DynamoDB, BigQuery, CosmosDB…) ?
- Criticité métier : impact business si le cloud hôte tombe ?
- Portabilité intrinsèque : l'app est-elle déjà conteneurisée / 12-factor ?
# Inventaire rapide avec AWS CLI (adapter pour GCP/Azure)
aws resourcegroupstaggingapi get-resources \
--output json | jq '.ResourceTagMappingList[].ResourceARN' > inventory-aws.txt
Score élevé couplage + criticité haute = candidat prioritaire à la stratégie de portabilité ou de mitigation.
3. Cartographier les points de lock-in
Catégories à évaluer systématiquement :
- Données : format propriétaire, egress fees, réplication cross-cloud
- Compute : Lambda vs Cloud Functions vs Azure Functions — divergences d'API
- Réseau : Peering interne, Private Link, équivalents sur chaque cloud
- Identité : IAM natif vs fédération externe (OIDC, SAML)
- Observabilité : CloudWatch vs Cloud Monitoring vs Azure Monitor
Outil de référence pour l'analyse lock-in : CNCF Cloud Native Landscape
4. Définir la stratégie de répartition
Patterns courants :
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 · 192 lines · 71 tokens per session scan A f8641ee6aef5
multi-cloud-strategist is a skill published in the GitHub repository khalilbenaz/claude-skills-collection (22 stars, last pushed 19d ago), licensed MIT. It adds 71 tokens to every session and 2,010 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.