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 jonathan-vella/apex-accelerator --skill azure-cloud-migrategit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/azure-cloud-migrate)<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/azure-cloud-migrate"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/azure-cloud-migrate/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/jonathan-vella/apex-accelerator/azure-cloud-migrate"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/azure-cloud-migrate.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.00098 | $0.00588 |
| Opus 5 | $0.00049 | $0.00294 |
| Sonnet 5 | $0.00020 | $0.00118 |
| Haiku 4.5 | $0.00010 | $0.00059 |
Grade A, and why
azure-cloud-migrate 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 5d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Cloud Migrate
This skill handles assessment and code migration of existing cloud workloads to Azure.
Rules
- Follow phases sequentially — do not skip
- Generate assessment before any code migration
- Load the scenario reference and follow its rules
- Use
mcp_azure-mcp_get_bestpracticesandmcp_azure-mcp_documentationMCP tools - Use the latest supported runtime for the target service
- Destructive actions require
ask_user— global-rules
Migration Scenarios
The scenarios documented today are listed below. For other source platforms
(GCP, on-premises, etc.), call mcp_azure-mcp_documentation with
command: "microsoft_docs_search" to research the target Azure service and
adapt the AWS-Lambda assessment workflow as a template.
| Source | Target | Reference |
|---|---|---|
| AWS Lambda | Azure Functions | lambda-to-functions.md |
No matching scenario? Use
mcp_azure-mcp_documentationandmcp_azure-mcp_get_bestpracticestools.
Output Directory
All output goes to <source-folder>-azure/ at workspace root. Never modify the source directory.
Steps
- Create
<source-folder>-azure/at workspace root - Assess — Analyze source, map services, generate report → assessment.md
- Migrate — Convert code using target programming model → code-migration.md
- Ask User — "Migration complete. Test locally or deploy to Azure?"
- Hand off to azure-prepare for infrastructure, testing, and deployment
Track progress in migration-status.md — see workflow-details.md.
Reference Index
Load these on demand — do NOT read all at once:
What ships with it
11 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/services/functions/assessment.md 7.8 KB
- references/services/functions/code-migration.md 6.7 KB
- references/services/functions/global-rules.md 3.3 KB
- references/services/functions/lambda-to-functions.md 12 KB
- references/services/functions/runtimes/csharp.md 5.5 KB
- references/services/functions/runtimes/java.md 6.4 KB
- references/services/functions/runtimes/javascript.md 8.6 KB
- references/services/functions/runtimes/powershell.md 5.4 KB
- references/services/functions/runtimes/python.md 6.4 KB
- references/services/functions/runtimes/typescript.md 3.5 KB
- references/workflow-details.md 1.8 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.
- 5d ago First seen · 57 lines · 98 tokens per session scan A a4921d9c614e
azure-cloud-migrate is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 588 once invoked, about $0.0005 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
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
enumerating-cloud-with-cloudfox
Map AWS and Azure attack paths and find exploitable misconfigurations with CloudFox.
infrastructure-as-code
Domain: DevOps & Cloud Engineering.
cloud-solution-architect
Design well-architected Azure cloud systems — 10 design principles, 6 architecture styles, 44 design patterns, technology choices, WAF pillars.
bicep-avm-mastery
Azure Verified Modules (AVM), Bicep best practices, and MCP-powered infrastructure as code for Azure.
foundry-agent-platform
Microsoft Foundry agent deployment, orchestration, and cloud-native AI service patterns.