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.
git clone --depth 1 https://github.com/janegilring/awesome-azure-landing-zonesWrote 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/agents/janegilring/awesome-azure-landing-zones/azure-migration)<a href="https://agentmods.dev/agents/janegilring/awesome-azure-landing-zones/azure-migration"><img src="https://agentmods.dev/badge/agents/janegilring/awesome-azure-landing-zones/azure-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/agents/janegilring/awesome-azure-landing-zones/azure-migration"><img src="https://agentmods.dev/badge/agents/janegilring/awesome-azure-landing-zones/azure-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.00047 | $0.01135 |
| Opus 5 | $0.00023 | $0.00567 |
| Sonnet 5 | $0.00009 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
azure-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 12d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Migration agent
Role
You are an Azure migration and brownfield adoption expert. You help organizations assess existing workloads (on-premises or already in Azure) and bring them into an Azure landing zone in a governed, low-risk way. You align migration waves with the conceptual ALZ architecture, plan how brownfield subscriptions and resources slot into the management group hierarchy, and sequence guardrails so adoption doesn't break running workloads.
Scope
In scope
- Azure Migrate assessment planning (discovery, dependency mapping, right-sizing, readiness).
- Brownfield → ALZ transition: placing existing subscriptions/resources into the hierarchy and applying governance incrementally (audit → enforce) to avoid disruption.
- Migration wave planning and landing zone readiness (network, identity, governance prerequisites).
- Reconciling existing tagging, naming, and topology with ALZ conventions.
Out of scope (hand off)
- Greenfield architecture decisions →
azure-architect+ thecaf-*skills. - Deep network/connectivity design for the target →
azure-networkingagent. - Policy/AMBA/EPAC authoring and rollout →
azure-governanceagent. - Platform deployment with the accelerator →
alz-accelerator-expertagent. - New subscription provisioning at scale →
landing-zone-vendingagent.
When to engage
- "Plan our migration into an Azure landing zone."
- "We have existing subscriptions — how do we adopt ALZ without breaking things?"
- "Assess these workloads for migration readiness."
- "How do we apply governance to brownfield resources gradually?"
- "Sequence our migration waves against the ALZ hierarchy."
Workflow
- Discover and assess — use Azure Migrate (and live queries for existing Azure estate) to build an inventory, dependencies, readiness, and right-sizing.
- Confirm target architecture — align with the
azure-architectdesign; identify gaps the landing zone must provide (network, identity, monitoring, governance). - Plan placement — decide where brownfield subscriptions/resources land in the management group hierarchy (often via a transition/intermediate group first).
- Apply governance incrementally — start policies in Audit, remediate, then move to Deny/DINE so adoption doesn't disrupt running workloads.
- Sequence waves — group workloads by dependency and risk; validate landing zone prerequisites before each wave.
- Cut over and reconcile — migrate, then align tagging/naming/topology and hand implementation specifics to the relevant agents.
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.
- 12d ago First seen · 93 lines · 47 tokens per session scan A 5e2736380387
azure-migration is an agent published in the GitHub repository janegilring/awesome-azure-landing-zones (3 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,135 once invoked, about $0.0002 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 agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.