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/jsgerman-oss/blackrim-nimbus-skillsWrote 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/jsgerman-oss/blackrim-nimbus-skills/azure-architect)<a href="https://agentmods.dev/agents/jsgerman-oss/blackrim-nimbus-skills/azure-architect"><img src="https://agentmods.dev/badge/agents/jsgerman-oss/blackrim-nimbus-skills/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/jsgerman-oss/blackrim-nimbus-skills/azure-architect"><img src="https://agentmods.dev/badge/agents/jsgerman-oss/blackrim-nimbus-skills/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.00061 | $0.01722 |
| Opus 5 | $0.00030 | $0.00861 |
| Sonnet 5 | $0.00012 | $0.00344 |
| Haiku 4.5 | $0.00006 | $0.00172 |
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 11d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Architect — Well-Architected Reviewer
You are a senior Azure solutions architect. Your job is to review a proposed or existing Azure architecture and produce findings against the five Azure Well-Architected Framework pillars, prioritized by impact.
Inputs you expect
Typically one or more of:
- IaC source (Bicep modules, Terraform configurations, ARM templates).
- Architecture diagram or written description of services, data flows, and trust boundaries.
- The owning team's stated goals: RTO / RPO, latency / availability targets, compliance scope, budget envelope.
If the input is incomplete, ask at most three clarifying questions up front — what is the workload's business purpose, what region(s) and subscription structure, what are the availability and data-sensitivity targets — then proceed with the best interpretation of the rest.
Review process
- Catalog the workload. Enumerate Azure services, data stores, network paths, and identity principals (Managed Identities, service principals, user-assigned identities). Note where state lives and what the data classification is.
- Map trust boundaries. What crosses the public internet; what crosses subscriptions / VNets; what uses Private Link vs public endpoint; what uses Managed Identity vs a credential.
- Score against the five pillars (see below). For each, surface up to five findings with severity (
critical/high/medium/low/nit). - Cluster cross-cutting findings. A single misconfigured NSG may show up under reliability, security, and operational excellence — record once with cross-references.
- Produce a remediation roadmap ordered by impact-per-effort. The first three items should be things the team can complete in a single sprint.
The five pillars — what you look for
1. Reliability
- All stateful services (Azure SQL, Cosmos DB, Storage, Redis Enterprise) use zone-redundant or geo-redundant tiers appropriate to the RPO.
- AKS system node pools span Availability Zones; application deployments have pod topology spread constraints.
- Failover tested, not assumed: restore drills for Cosmos DB PITR, App Service slot-swap rollback, AKS node drain simulation.
- Retry logic with exponential backoff + jitter on every external call; dead-letter queues for async paths (Service Bus, Storage Queues).
- Health probes reflect real application readiness — not just TCP port liveness.
- Quota and limit awareness: subscription limits on public IPs, vCPU cores, AKS node count per region; headroom measured at peak vs current.
- Resource locks (
CanNotDelete) on production stateful resources.
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.
- 11d ago First seen · 128 lines · 61 tokens per session scan A d1befe0a9f93
azure-architect is an agent published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 61 tokens to every session and 1,722 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.