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 iblai/government-agents --skill microsoft-entra-idgit clone --depth 1 https://github.com/iblai/government-agentsWrote 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/iblai/government-agents/microsoft-entra-id)<a href="https://agentmods.dev/skills/iblai/government-agents/microsoft-entra-id"><img src="https://agentmods.dev/badge/skills/iblai/government-agents/microsoft-entra-id/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/iblai/government-agents/microsoft-entra-id"><img src="https://agentmods.dev/badge/skills/iblai/government-agents/microsoft-entra-id.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.00040 | $0.00666 |
| Opus 5 | $0.00020 | $0.00333 |
| Sonnet 5 | $0.00008 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
microsoft-entra-id 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsoft Entra ID
What it is
Microsoft Entra ID (formerly Azure Active Directory) is the cloud identity and access management platform underpinning Microsoft 365 GCC and GCC High environments used by federal and state agencies. It manages user accounts, group memberships, MFA enrollment, conditional access policies, and device compliance, and serves as the identity provider for most agency SaaS applications.
When to use this skill
- Looking up a user's account status, last sign-in, department, and license assignments during IT support
- Checking MFA enrollment and SSPR registration for a specific user
- Reviewing group memberships and conditional access policy assignments
- Initiating supervised password-reset workflows (requires approval chain)
- Provisioning or deprovisioning accounts as part of onboarding/offboarding workflows
Credentials
This skill authenticates using variables from the OpenClaw daemon env file ~/.openclaw/.env (template: .env.example). Required variables:
ENTRA_TENANT_ID- Azure AD / Entra tenant ID (GUID)ENTRA_CLIENT_ID- registered app client ID with appropriate MS Graph permissionsENTRA_CLIENT_SECRET- registered app client secretENTRA_GRAPH_ENDPOINT- Microsoft Graph base URL (GCC High:https://graph.microsoft.us; GCC:https://graph.microsoft.com)
Key operations
POST /oauth2/v2.0/token— obtain a client-credentials access token for MS GraphGET /v1.0/users/{userPrincipalName}— retrieve user profile, account status, and last sign-inGET /v1.0/users/{id}/memberOf— list group and role membershipsGET /v1.0/users/{id}/authentication/methods— enumerate registered MFA methodsGET /v1.0/users/{id}/assignedLicenses— list Microsoft 365 license assignmentsPOST /v1.0/users/{id}/invalidateAllRefreshTokens— revoke all sessions (requires User.ReadWrite.All)PATCH /v1.0/users/{id}— update account properties (requires appropriate write permissions)
Notes
- GCC High tenants use the
graph.microsoft.usendpoint and a separate authority (login.microsoftonline.us); using the commercial endpoint will fail. - Write operations (password reset, account enable/disable) require User.ReadWrite.All or a delegated admin role; all writes must go through an approval workflow.
- Conditional access policies and privileged identity management (PIM) roles control what the service account can perform; coordinate with the agency IAM team.
- Audit logs for all read/write operations are retained in Entra ID Sign-in and Audit logs for 30 days by default (extend via Log Analytics integration).
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 · 40 lines · 40 tokens per session scan A 4dc51ea83433
microsoft-entra-id is a skill published in the GitHub repository iblai/government-agents (10 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 666 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
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.