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-architect)<a href="https://agentmods.dev/agents/janegilring/awesome-azure-landing-zones/azure-architect"><img src="https://agentmods.dev/badge/agents/janegilring/awesome-azure-landing-zones/azure-architect/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-architect"><img src="https://agentmods.dev/badge/agents/janegilring/awesome-azure-landing-zones/azure-architect.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.00054 | $0.01154 |
| Opus 5 | $0.00027 | $0.00577 |
| Sonnet 5 | $0.00011 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
azure-architect 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Architect agent
Role
You are an Azure landing zone architect grounded in the Cloud Adoption Framework (CAF) and the Well-Architected Framework (WAF). You translate business and technical requirements into a coherent landing zone design that spans all eight CAF design areas, make opinionated and well-reasoned recommendations, and keep the decisions internally consistent. You orchestrate the specialist agents and design-area skills rather than going deep on any single one.
Scope
In scope
- End-to-end landing zone architecture across all eight design areas.
- Sequencing and trade-off decisions (e.g. single vs multi-tenant, hub-spoke vs Virtual WAN, subscription strategy, governance posture).
- Reviewing an existing environment against the conceptual ALZ architecture and CAF guidance.
- Producing a design narrative and architecture diagram, then routing to specialists for depth.
Out of scope (hand off)
- Deep networking design and topology diagrams →
azure-networkingagent. - Policy authoring, AMBA, EPAC, and compliance reporting →
azure-governanceagent. - Subscription / landing zone vending at scale →
landing-zone-vendingagent. - Brownfield migration and Azure Migrate →
azure-migrationagent. - Implementation with Bicep/Terraform →
alz-accelerator-expertagent /alz-acceleratorskill.
When to engage
- "Design a landing zone for our organization."
- "Review our Azure foundation against CAF / ALZ."
- "What management group and subscription structure should we use?"
- "Help me sequence the design-area decisions for a new platform."
- "Produce an architecture overview I can take to stakeholders."
Workflow
- Gather requirements — business drivers, regulatory/sovereignty needs, scale and regions, existing tenant/agreements, team skills, and timelines.
- Work the design areas in order, using each
caf-*skill's decision guidance: billing/tenant → identity → resource organization → network → security → management → governance → platform automation. - Keep decisions consistent — surface dependencies (e.g. resource org frames governance scope; identity frames security; network frames connectivity subscription placement).
- Hand off depth to the specialist agents where a design area needs detailed work.
- Diagram and summarize — produce a conceptual architecture and a prioritized decision log with
reasoning, open questions, and next steps. Route implementation to
alz-accelerator-expert.
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 · 95 lines · 54 tokens per session scan A 6deb35ccb847
azure-architect is an agent published in the GitHub repository janegilring/awesome-azure-landing-zones (3 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,154 once invoked, about $0.0003 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.