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 HermeticOrmus/LibreSecOps-Claude-Code --skill azure-identity-patternsgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/azure-identity-patterns)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/azure-identity-patterns"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/azure-identity-patterns.svg" alt="Measured on agentmods" 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.00000 | $0.02220 |
| Opus 5 | $0.00000 | $0.01110 |
| Sonnet 5 | $0.00000 | $0.00444 |
| Haiku 4.5 | $0.00000 | $0.00222 |
Grade A, and why
azure-identity-patterns 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 6d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Identity Patterns
Entra ID security patterns, Conditional Access design, Managed Identities, Privileged Identity Management, and service principal governance.
Knowledge Base
Entra ID Security Architecture
Entra ID (formerly Azure Active Directory) is the identity control plane for all Microsoft cloud services. It handles:
- Authentication: Who are you? (MFA, passwordless, FIDO2, certificate-based)
- Authorization: What can you access? (Conditional Access, Azure RBAC, app roles)
- Governance: Should you still have access? (Access Reviews, Entitlement Management, PIM)
Two separate role systems exist and are commonly confused:
| System | Controls | Example Roles |
|---|---|---|
| Entra ID Roles | Directory operations (user management, app registration, Conditional Access) | Global Administrator, User Administrator, Application Administrator |
| Azure RBAC Roles | Resource operations (VMs, storage, databases) | Owner, Contributor, Reader, custom roles |
A Global Administrator can elevate to Azure RBAC through "Access management for Azure resources" toggle, but by default the two systems are independent.
Conditional Access Policy Evaluation
Conditional Access policies are evaluated AFTER first-factor authentication but BEFORE access is granted. The evaluation logic:
- All policies are evaluated simultaneously (not in order)
- If ANY policy's conditions match AND its grant controls are not satisfied, access is DENIED
- If multiple policies match, ALL grant controls from all matching policies must be satisfied
- Session controls from all matching policies are combined
- Exclude takes precedence over include for user/group targeting
- Report-only mode evaluates but does not enforce (useful for testing)
Managed Identity Types
| Type | Lifecycle | Scope | Use Case |
|---|---|---|---|
| System-assigned | Tied to the resource. Created when enabled, deleted when resource is deleted. | Single resource. 1:1 relationship. | Simple workloads where one resource needs one identity. |
| User-assigned | Independent resource. Created and deleted separately. | Can be assigned to multiple resources. Many:many. | Shared identity across multiple resources. Survives resource deletion. |
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.
- 6d ago First seen · 207 lines · 0 tokens per session scan A 86f69572b085
azure-identity-patterns is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,220 tokens. 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
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.