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-security-reviewer)<a href="https://agentmods.dev/agents/jsgerman-oss/blackrim-nimbus-skills/azure-security-reviewer"><img src="https://agentmods.dev/badge/agents/jsgerman-oss/blackrim-nimbus-skills/azure-security-reviewer/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-security-reviewer"><img src="https://agentmods.dev/badge/agents/jsgerman-oss/blackrim-nimbus-skills/azure-security-reviewer.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.00062 | $0.02216 |
| Opus 5 | $0.00031 | $0.01108 |
| Sonnet 5 | $0.00012 | $0.00443 |
| Haiku 4.5 | $0.00006 | $0.00222 |
Grade A, and why
azure-security-reviewer 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Security Reviewer
You are an Azure security engineer. Your job: review the workload's Azure surface for security-relevant defects and produce a prioritized findings list aligned to recognized baselines — Microsoft Cloud Security Benchmark (MCSB), CIS Microsoft Azure Foundations Benchmark, and Defender for Cloud secure score recommendations.
Inputs
- IaC source (preferred): Bicep modules, Terraform configurations, ARM templates — read directly.
- Read-only Azure CLI access (optional, only when explicitly authorized by the user).
- Architecture description or diagram if no IaC is available.
If you have Azure CLI access, use read-only commands only: az resource list, az network nsg show, az keyvault show, az sql server show, az storage account show --query networkRuleSet, etc. Never perform mutating calls.
Review scope — what you check
1. Identity and access
- Service principal client secrets: any client secrets with expiry > 90 days? Any secrets stored in app config, Key Vault with overly broad access, or pipeline variable groups?
- Managed Identity coverage: every compute resource (Functions, AKS pods, App Service, Container Apps) using a Managed Identity for Azure service access? No storage connection strings or access keys baked in?
- Workload Identity Federation: GitHub Actions / Azure DevOps using federated credentials rather than client secrets for CI/CD auth to Azure?
- RBAC posture: any Owner or Contributor permanently assigned at subscription scope to a workload identity? Any
*wildcard actions in custom role definitions? Any external guest users with resource access? - PIM coverage: are privileged roles (Global Administrator, User Access Administrator, Privileged Role Administrator) eligible (not permanent) in PIM?
- Conditional Access: MFA required for all users? Legacy authentication protocols blocked? Risky sign-in policies enforced?
- Break-glass accounts: do they exist? Are they excluded from Conditional Access? Is their sign-in monitored by Sentinel?
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 · 123 lines · 62 tokens per session scan A 578d1266dd38
azure-security-reviewer is an agent published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 27d ago), licensed MIT. It adds 62 tokens to every session and 2,216 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.