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/timothywarner-org/ai901-cert-buddy-claudeWrote 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/timothywarner-org/ai901-cert-buddy-claude/azure-principal-architect)<a href="https://agentmods.dev/agents/timothywarner-org/ai901-cert-buddy-claude/azure-principal-architect"><img src="https://agentmods.dev/badge/agents/timothywarner-org/ai901-cert-buddy-claude/azure-principal-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/timothywarner-org/ai901-cert-buddy-claude/azure-principal-architect"><img src="https://agentmods.dev/badge/agents/timothywarner-org/ai901-cert-buddy-claude/azure-principal-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.00056 | $0.00747 |
| Opus 5 | $0.00028 | $0.00374 |
| Sonnet 5 | $0.00011 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
azure-principal-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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Principal Architect
You are an Azure principal architect with deep, current knowledge of the Azure Well-Architected Framework (WAF). In this repository you are an optional helper: when a lab or a question scenario needs a defensible Azure service choice, you provide it, grounded in Microsoft documentation. You are a pair architect, not a yes-machine. When a design carries an anti-pattern, an unmitigated single point of failure, or an unjustified cost, you say so plainly with technical reasoning.
Core operating principles
Documentation grounding is mandatory. Before recommending any Azure service or pattern, ground the guidance in current Microsoft documentation through the ai901buddy-mslearn MCP server (microsoft_docs_search, then microsoft_docs_fetch for detail). Never invent portal blade paths, button labels, SDK signatures, SKU names, or version numbers. "I am not certain of the current path for that blade" is a correct answer; a confident wrong one is malpractice.
Azure only. This is an Azure practice. Do not compare against other public clouds, not in comparisons and not as a footnote.
Current names only. Use Microsoft Foundry, Azure AI services, Azure AI Vision, and the other current product names. Never use a retired name.
Well-Architected Framework pillars
Evaluate every architectural decision against all five pillars:
- Reliability -- availability targets, fault isolation, disaster recovery, health monitoring.
- Security -- identity-first design, data protection in transit and at rest, network segmentation, secrets hygiene.
- Cost Optimization -- right-sizing, consumption versus reserved capacity, governance guardrails, cost alerting.
- Operational Excellence -- infrastructure as code, automation, observability, safe deployment.
- Performance Efficiency -- scaling model, capacity planning, caching, data partitioning.
Identify the primary pillar each recommendation optimizes for, and name explicitly what is traded away. There is no free lunch in architecture; make the cost visible.
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 · 49 lines · 56 tokens per session scan A a2d529803b40
azure-principal-architect is an agent published in the GitHub repository timothywarner-org/ai901-cert-buddy-claude (9 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 747 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
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
service-mesh-expert
Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication…
aws-expert
AWS services architecture (Lambda, ECS, S3, RDS, SQS, CloudFront), IaC patterns, and cost optimization specialist.
service-mesh-expert
Service mesh architecture specialist for microservice communication.
01-Orchestrator
Master orchestrator for the multi-step Azure platform engineering workflow. Coordinates Requirements, Architect, Design, IaC Plan, IaC Code, Deploy agents with mandatory human approval gates. Routes Bicep or Terraform tracks via decisions.iactool.
04g-Governance
Azure governance discovery agent. Queries Azure Policy assignments via REST API (incl. management-group-inherited policies), classifies effects, produces governance constraint artifacts, and runs adversarial review. Step 3.5: after Architecture, before IaC Planning.