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.
npx skills add niels-emmer/myace --skill azure-identitygit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/skills/niels-emmer/myace/azure-identity)<a href="https://agentmods.dev/skills/niels-emmer/myace/azure-identity"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/azure-identity/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/skills/niels-emmer/myace/azure-identity"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/azure-identity.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.00035 | $0.00857 |
| Opus 5 | $0.00017 | $0.00428 |
| Sonnet 5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
Azure Identity Design 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Identity is the security boundary in Azure. This skill is the Azure-specific
companion to iac-expert's "Managed Identity Over Long-Lived Secrets" rule:
it explains the identity options Azure offers, when to use each, and how to
design so that long-lived secrets are the exception, not the default.
When to use it
Any time you're designing or reviewing how an Azure workload authenticates — a new service, a service-to-service call, a CI/CD pipeline deploying to Azure, or a human accessing the portal/CLI.
The identity options, and when to use each
Managed identity — the default for any Azure-hosted workload (App Service, Functions, VMs, AKS, Logic Apps, etc.). Azure automatically rotates the backing credential; your code just requests a token. Use this for service-to-service access between Azure resources. Prefer a user-assigned managed identity when you need the identity to outlive a single resource or be shared across several; system-assigned when the identity is tied to exactly one resource.
Workload identity federation — for non-Azure or external workloads (a GitHub Actions workflow, a Kubernetes cluster outside Azure, a third-party SaaS) that need to act as an Azure identity. Configure a federated identity credential on an app registration so the external workload's OIDC token is trusted directly — no client secret exchanged. This is the modern replacement for service principals with secrets in CI/CD.
Service principal with a client secret — the legacy option. Only
acceptable when the target genuinely has no managed-identity or federation
option. If you must use one: store the secret in Key Vault, reference it by
ID, scope its RBAC to least privilege, and rotate it on a short, documented
cadence. Treat any new client secret as a documented exception per
iac-expert's exception-documentation skill.
Human access — Entra ID accounts with MFA and conditional access. No shared accounts, no standing admin credentials in code or config. Use Privileged Identity Management (PIM) for just-in-time elevation to privileged roles rather than permanent standing access.
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 · 74 lines · 35 tokens per session scan A 71d0f60d5bd2
Azure Identity Design is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 857 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 skills, from other repositories
detecting-azure-service-principal-abuse
Detect and investigate Azure service principal abuse including privilege escalation, credential compromise, admin consent bypass, and unauthorized enumeration in Microsoft Entra ID environments.
detecting-azure-lateral-movement
Detect lateral movement in Azure AD/Entra ID environments using Microsoft Graph API audit logs, Azure Sentinel KQL hunting queries, and sign-in anomaly correlation to identify privilege escalation, token theft, and cross-tenant pivoting.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations.
loom-prometheus
Prometheus monitoring and alerting for cloud-native observability.
drawio
WORKFLOW SKILL — Generate Azure architecture diagrams in .drawio via simonkurtz-MSFT MCP server (full Azure icon set, batch creation, transactional mode). Covers architecture, dependency, runtime-flow, and as-built diagrams. WHEN: 'draw.io diagram', 'Azure architecture diagram', 'as-built diagram', 'runtime flow…